Control who can visit your Scroll site by restricting access to a select group of readers.
To protect access to your site you can choose from two options: access tokens and single sign-on (SAML SSO).
Crucially, both options work independently of Confluence use seats and allow you to restrict access to your Confluence-sourced content without impacting your Confluence license cost.
Access tokens are a lightweight and quick way to password-protect your Scroll site. Once set up, site visitors who received a valid token (password) from you will be able to log into your site.
For increased protection, opt for the SAML single sign-on option. Once authenticated in your identity provider application, your users will be able to seamlessly access your help center without having to authenticate again.
To learn more about use case scenarios and benefits of authenticated Scroll Sites, see Publish Confluence Content without Anonymous Access in our Learning hub.
Choose Between Tokens and SAML Single Sign-On
Both options restrict who can read your site, and neither affects your Confluence license costs. This table compares them:
|
|
Token protection |
SAML single sign-on |
|---|---|---|
|
Who the credential belongs to |
A shared token, not tied to a user |
Each user's own identity provider account |
|
Where users log in |
The Scroll Sites Site |
Your identity provider |
|
Can appear in a URL |
Yes, if appended as |
No |
|
Session length |
1 hour, or until the browser session ends |
Managed by your identity provider |
|
Setup effort |
Minutes, with no external service required |
Requires a SAML 2.0 identity provider |
Recommended Reading
Publishing with Scroll Sites keeps your Confluence instance private with no anonymous access required. This Rock the Docs guides explain why that matters:
-
Publish Confluence Content Without Anonymous Access explains how publishing a separate, secure website keeps Confluence off the internet.