Internal pages (organization only)

Some pages aren’t for the public and aren’t right for a shared password either: an internal dashboard, a team runbook, a preview that only your colleagues should see. Bailey lets you make a site organization-only: anyone signed in to Bailey as a member of your organization can open it, and nobody else can.

Unlike a password, there’s nothing to hand around. Each person signs in with their own account, and you decide who’s in the organization.

Turn it on

Open your project → Settings → Who can see this site? → choose Organization members.

From now on, opening the address sends visitors through a quick sign-in. If they’re already signed in to Bailey and belong to your organization, they go straight through, no extra step. If they’re not a member, they’re told they don’t have access.

Make it the default for your whole organization

If most of what your team builds is internal, you shouldn’t have to remember this setting every time. An organization can decide that every new site starts out organization-only.

Open Organization → New sites → set the default audience to Organization members only.

Someone on your team creates a site — from the dashboard, or by asking their AI assistant.
It comes into the world reachable only by your members. Nobody has to think about it.
When a site really is meant for the public, whoever owns it switches that one site to Public. Going out to the world becomes a decision, instead of the thing that happens by accident.

Who counts as a member

Anyone in your organization, however they got there:

people who joined because they signed up with your organization’s email domain,
people you invited by email (a freelancer or partner with any address works exactly the same),
and, later, people who sign in through your company’s identity provider.

Access follows membership, not the email address. Remove someone from the organization and they lose access.

The three levels

In the same place you can switch a site between:

Public: anyone with the address can open it.
Organization members: only signed-in members of your organization (this page).
Password: one shared password for everyone, no accounts; see Password-protect a site.

What it protects, and what it doesn’t

Organization-only covers your whole published site: the page and every image, style, file, and any data the page collects. There’s no back door through a direct link.

Private, per-member data

Because each member signs in on an organization page, that page can offer everyone their own private space — a personal journal, a saved draft, a goal they set and pick up next time. Each member reads back only their own entries; another member can’t see them, and neither can you, the site owner. It’s the natural fit for a logbook, a per-person progress tracker, or private notes.

This only works on an organization page, because it’s the only place a page knows who’s signed in — a public page never learns who’s browsing it, by design. If you (or your AI assistant) are building the page, this is the owned bucket read back with store.mine; see the SDK guide.