A space sits on one rung of who can view it, and a new one is private until you say otherwise. Each rung has a name in the Share dialog and a visibility value that deploy, share_space, get_space and the CLI all use:
| Share dialog | visibility | Who can open it |
|---|---|---|
| Only people who were invited | private | You and the people you invite; only you add people. The default. |
| … with “let them invite others” | members | The same people, and they may invite more. On an organization's space, its members too. |
| Everyone on the <team> team | — (the Share dialog only) | Everyone on one of your teams, plus anyone you invite. |
| Anyone who signs in | signed_in | Anyone with the link, once they sign in: no guest list to keep, and every read has a name. Worker spaces allowed. |
| Anyone with the link | public | Anyone with the link, no sign-in. Static spaces only. Tick “show it on my profile” and it is also listed there, in the sitemap and in search engines. |
get_space reports the same visibility, and the flags behind it: open (anyone with the link), signedin, listed (on your profile and in search), and public — an older name for “members may invite”, which does not mean anyone can open the space.
Set the rung with access: { visibility, emails } on the deploy that creates the space. An update deploy keeps whatever rung the space has, so a redeploy never un-shares anything — leave visibility out unless you mean a wider audience; “publish” alone means private. Change a live space's rung with share_space or the Share dialog.