Skip to main content
A public Site can ask visitors for a password before it opens. Anyone who has the address and the password can open it, signed in or not. Use it to share a page with people outside your company’s member list, such as event guests, without opening it to everyone.

Who is asked for the password

The Site’s owner and company admins aren’t asked while they’re signed in. Everyone else is, members the Site is shared with included. Until the Sites gateway is on for your company, no one is asked: a public Site with a password opens only for its owner and company admins. While a password is set, shares don’t open this site: people you’ve shared it with type the password like everyone else and can’t edit or copy it. A share grants nothing while the password is set:
  • View: the holder opens the Site by typing the password, like any visitor.
  • Edit: the holder can’t read or change the Site’s drafts or branches. Only the owner and company admins can.
  • Copy: the holder can’t copy the Site.
The Site also leaves members’ sites menu. Company admins still see it there. Remove the password, or make the Site private, and shares work again. A private Site keeps its password, so shares stop again once it’s public.

What a visitor sees

In place of the Site, a visitor sees This site is password protected, a Password field and Open site. The page names nothing about the Site, and search engines are asked not to index it.
  • Each page load asks again. The password opens the Site for that page load only. A reload, a new tab or coming back asks again, and an open page asks again after 8 hours.
  • A wrong password shows “That password isn’t right. Try again.” The same message shows when the Site can’t be opened at all.
  • Too many tries shows “Too many tries. Wait a few minutes, then try again.”
Changing or removing the password ends every page that’s open with the old one.

Password rules

A Site password has at least 6 characters, at most 72 bytes, and at least one letter, one digit and one symbol. A symbol is any character that isn’t a letter or a digit, a space included. Nothing is trimmed, and nothing else is required. A refused password says which rule it broke; see Errors. Only a public Site can be given a password. A branch never can: it’s always private.

Private Sites keep their password

Making a password Site private keeps its password. Making it public again asks visitors for that same password. Only removing the password takes it away. The API never returns a password. The v2026-10 Member and company APIs show whether a Site has one with two fields on every Site: Read password_updated_at to know whether a Site has a password, and password_protected to know whether visitors are asked for it now. A protected Site’s visibility is public, so in a company’s list of Sites, filter[visibility]=public returns protected Sites too. Check password_protected to tell them apart.

Set, change or remove the password

The Site’s owner, or a company admin, sets the password.
Site passwords need the Sites gateway, which isn’t on for every company yet. Until it is, you can remove a password but not set one. To turn it on, contact support.

In the Fluid admin

Open the Site under Website > Sites and use its Password card, on a company Site or a member’s: Add a password or Change password, type it, then Save password. Remove password asks you to confirm. The page never keeps the password in its form. The card also shows when a private Site has kept its password. See Sites in the admin.

With the CLI

With Sites plugin 0.1.503 or later, in the Site’s folder, with the owner’s login:
set asks for the password twice at a prompt that doesn’t echo it, and never takes it as an argument. Where there’s no terminal, such as in CI, pipe it in:
--public makes a private Site public behind the password in one change, so it’s never open without it. fluid sites visibility and fluid deploy --public keep a Site’s password, and a protected Site shows as public (password).

In Mist

Open the Site’s Settings and use the Password card: Set password, or Change, type it, then Save password. On a private Site, use Make public and protect. Remove asks you to confirm. Mist never stores, logs or shows the password, and its agent never sees one: it can open the Password card for you, but won’t set a password itself.

From an AI client

The Fluid MCP server has site_password_set and site_password_remove for admins, and my_site_password_set and my_site_password_remove for your own Sites. See the tools.
A password you give an AI client passes through its model and stays in the chat. Type it yourself in Mist or with fluid sites password set when that matters.

With the API

As the Site’s owner, change the site through the Member API:
  • { "password": "..." } sets or changes the password. { "password": null } removes it.
  • { "visibility": "public", "password": "..." } makes a private Site public behind the password in one change.
As a company admin, change the member site through the company API, with application_themes.update:
Use an admin’s own login. A company API token never changes a member’s Site, and changes a company Site only where Fluid has turned that on; see Deploy from CI or an agent.

Errors

A refused password change answers 422 in the usual error shape. error.details.error names the code, and for a password rule, error.details.password holds the message: