Public Pages
A team organisation can present itself to the world. That presentation is the public page. It is off by default. Two switches control what the world sees. The switches are independent.
What the public page is for
The public page is the organisation as a card. It is meant to read the same way a person reads in NUU Profiles. A visitor sees a name, a tagline, a picture, and a short story.
The page is not the place where you manage members. Management stays inside the signed-in view. The public page is only what you choose to show.
A personal organisation never has a public page. A person already has a profile. See Personal and Team Organisations.
The two switches
The first switch turns the public page on or off.
When the page is off, only members see the organisation. The browse screen does not list it. A visitor who tries the public address sees that the organisation is not found.
When the page is on, the organisation appears on the browse screen. Anyone can open the public page. The address uses the stable identity, so it does not depend on the display name. See Identity and Slug.
The second switch shows or hides the public roster.
The public roster is the member list on the public page. Each row shows a name, a picture, and a label if one is set. If a member has no label, the page shows them as a member.
If the roster is off, the page still shows how many members there are. It does not show who they are. The page says that the member list is private.
You can change the roster switch only when the public page is on.
What the page shows
An admin edits the public fields. Those fields are:
- name
- tagline (one line under the name)
- description (longer text, with markdown)
- location
- website
- founded date
- dissolved date
- extra links, each with a label and a URL
- picture
Dates can be a year, a year and a month, or a full day. Leave the dissolved date empty if the organisation is still active.
The browse screen shows a shorter card: name, tagline, picture, and member count.
Who can edit
Only an owner or an admin can edit the public page and the two switches. A member can see the organisation. A member cannot change what the world sees.
You can preview the public page before you save. Preview uses the fields you have on screen, including the roster choice.
Why the page starts private
A new team is often not ready to be seen. Names change. Membership is still in flux. The product keeps the page off until an admin turns it on.
Making the page public is a separate act from creating the organisation. Create first. Invite people. Then decide what the world may see.