Audiences & access
Audiences let you show different sections to different groups of visitors. For example, you might have an Internal audience for team members and an External audience for clients — and show some sections only to one group.
What an audience is
Section titled “What an audience is”An audience is a named viewer group. Each audience has a display name, an optional color to identify it at a glance, and typically a password that visitors enter to access it. Visitors choose their audience and enter the password when they first arrive at your portal.
Assigning a section to an audience
Section titled “Assigning a section to an audience”Hover over a section to reveal its editing controls. In the header bar at the top of the section you will see an audience pill. Click it to open the audience picker.
The picker shows a checkbox list of all configured audiences. Check one or more audiences to restrict the section to those groups. Uncheck all of them to make the section visible to everyone.
- No audiences checked — the section is visible to all visitors (no restriction)
- One or more audiences checked — only visitors who have authenticated as one of those audiences will see the section
Changes take effect in your working copy. The section will be filtered for viewers once you save and publish.
The default audience
Section titled “The default audience”On Supabase-backed sites your portal has a default audience that is set up automatically when the site is created. The default audience cannot be deleted. It is typically used as the starting point for all visitors — your developer can explain how audiences are structured for your specific site.
Sign-ins: who can enter an audience
Section titled “Sign-ins: who can enter an audience”On Supabase-backed portals, viewers log in with a username and password, not by picking an audience from a list. Each sign-in belongs to exactly one audience and sees exactly what that audience sees.
That means you can give each partner their own:
| Audience | Sign-ins |
|---|---|
| External Agencies | agency1, agency2, agency3 |
Remove agency2 and the other two are untouched. Add agency4 and it immediately sees the same content as the rest — you never re-configure the audience itself.
Manage them under Site Settings → Viewer Access: expand an audience and use Add sign-in, or Edit an existing one to relabel it or set a new password. Passwords need at least 8 characters — pick something you can dictate over the phone, since someone will have to type it.
An audience with no sign-ins cannot be entered by anybody. A new audience starts that way — add at least one sign-in to make it usable.
Managing audiences
Section titled “Managing audiences”How you manage audiences depends on how your portal is set up:
Supabase-backed sites — you can create, rename, recolor, and delete audiences directly in the portal. Go to Site Settings → Viewer Access to manage them. A new audience takes no password of its own; add sign-ins to it instead (see above). You can also enable or disable the password requirement from that screen — if the password is turned off, all published sections are visible to anyone regardless of audience assignment.
Deleting an audience deletes its sign-ins with it, locking out anyone using them.
Password-only sites — audiences are configured in the site’s environment variables by your developer and are shown in Site Settings as read-only. These portals have no per-partner sign-ins: viewers pick an audience and enter its shared password. Contact your developer to update the audience list.
Seeing it from the audience’s side
Section titled “Seeing it from the audience’s side”To check what an audience actually ends up with — and to look up a password to share — use the Audience details page, linked near the bottom of the sidebar.