PublicViewsReference
Look and branding
How a published view is laid out, how each record is named, and how it carries your brand instead of ours. None of it changes what a viewer can see: that is decided by which attributes are visible, and nothing on this page can add one.
Where the Look settings are
The three steps to a first publish ask nothing about looks: a new view is a table, with no logo and no colour, and that is a finished view. Once it has been published, open it and use the editor’s Look row. Its summary reads like Table · light · no badge, and opening it shows every setting below. Changes wait for the Save button like every other row, and a live view shows them on the next load.
Table, board, single record
| Layout | What a viewer gets | Suits |
|---|---|---|
| Table | One row per record, one column per visible attribute. A viewer can open any row to see all of its attributes on a page of its own. | Lists anybody might scan, sort or search. Every new view starts here. |
| Board | Columns of cards, one column per option of a status or select attribute. | A pipeline or a set of stages, where where-it-is matters more than the details. |
| Single record | One record as a sheet, attributes top to bottom: the first record the view publishes. | A view that publishes exactly one record, such as one client's own account. |
Grouping a board
A board needs Group the columns by: a status or select attribute that the view already shows. Records with no value for it get a column of their own. If the view shows no attribute of either type, Board is greyed out and the Look row says why, with a link to choose attributes.
Multi-select attributes are deliberately not offered. A record with three options would be filed under the first and silently missing from the other two columns, which neither you nor your viewer could see.
The grouping attribute has to be visible because a board is built from what the viewer receives. If you later hide it, the Look row’s grouping comes up empty and you pick again.
Naming each record
- Title each record by. Which attribute names a record: on board cards, at the top of a single-record sheet, and on the page a viewer opens from a table row. Only attributes the view already shows are offered, and choosing one never adds an attribute to the view.
- Show an image from. A text attribute holding an
httpsimage address, drawn before each record’s name. A company logo field is the usual one. It is optional.
Logo, colour and theme
- Logo URL. An
httpsaddress for an image you already host. We store no files, so the logo stays wherever you keep it. - Brand colour. A hex value such as
#2b6cb0. It colours the rule across the top of the view, the primary button and the row tint. We do not check it for contrast, so pick one your viewers can read against. - Theme. Follow the reader’s device, Always light or Always dark. Force one if your brand only works in it.
The same logo, colour and theme are on the password or email screen a viewer meets first, as well as on the view itself. A link that does not work at all shows none of them, so a stranger with a mistyped address cannot tell whose view it would have been.
The PublicViews badge
Every view starts with a small Made with PublicViews badge. On Starter and Pro you can hide it. On the free plan the switch is disabled and says which plan removes it.
- One view at a time: Hide the “Made with PublicViews” badge, in the Look row.
- Every view at once: Settings → General, under Made with PublicViews badge. It says how many of your views show it, and a view you make later still starts with the badge on.
Custom domains are not available on any plan; every view is served from its PublicViews link. Why, and what happens to a hostname pointed at us.
Looks never change exposure
Every control on the Look row chooses from attributes the view already shows. A title, an image, a board column: none of them can publish an attribute you left hidden. To change what a viewer sees, use the Columns row.
Anything here wrong, or missing? support@publicviews.app.