Protection

Protection restricts who can see your site or parts of it, and it is a Pro plan feature. Reach for it when you want to share work in progress with a client, gate a private gallery, or publish internal documentation that should stay off the open web.

There are three levels.

Protect the whole site

Choose the level from the site settings:

  • Public, which is the default. Anyone can view the site.
  • Password protected. Every visitor must enter a password you set before any page will load, and the site’s media is covered as well.
  • Workspace protected. Only signed-in members of your workspace get in, so you never distribute a password and access follows your team.

The same setting is available through the API as protectionType, with pagesPassword for the site password. Switching to password protection requires a password in the same request unless one is already stored.

Protect a single page

On a site at any level, you can give an individual page a password of its own. Visitors see a password prompt instead of the content, and any media embedded in the page is protected along with it.

A page with its own password opens with that password and no other:

  • On a public site, the rest of the site stays public, so you can mix public and protected pages freely. Pages with different passwords do not open each other.
  • On a password-protected site, the site password does not open the page, and the page’s password does not open the rest of the site.
  • On a workspace-protected site, the page’s password lets in visitors who are not members, to that page only.

A page with its own password is listed nowhere on the site: not in menus, section listings, tag pages, feeds, the sitemap, or search results, and it shows no tags of its own. Visitors reach it by its link, so share the link along with the password. Pages that share the same password all open when it is entered once. A browser keeps up to 20 unlocked passwords for a site at a time, and each page with its own password counts as one, so on a site with more such pages than that, the rest ask for the password when they are opened.

On a workspace-protected site, members who are signed in to the site can read the page without its password. On a public or password-protected site, members enter the page’s password like any other visitor.

Page passwords can be set in the page editor or through the API with the password field; an empty string removes the protection again.

Media follows its page

There is no separate password on an individual file. A media file is protected because the page it belongs to is protected, or because the whole site is protected, and it opens for visitors who can open a page that shows it. The site’s own images, such as its logo and author photos, appear on every page, so they open for any visitor who can open a page of the site. To share a protected file, protect the page that contains it.

Sharing a password

Anyone with the password can view the protected content, so treat it like a shared link: pick a password you are comfortable distributing and share it through a channel you trust. For a known team, workspace protection avoids sharing a password at all. For content that should be private to you alone, keep it as a draft instead of deploying it.

Repeated attempts

Repeated wrong passwords are slowed down, and the visitor is asked to wait and try again. Signing in to a workspace-protected site works the same way.