Until this release a workspace had one door: it was public, or it was behind one private link, or it had one password. That works right up until two different audiences need two different views of the same documentation. This release replaced the single door with a set of rules.
New Several private links per workspace. A private workspace can carry more than one named private link, so you can hand a different URL to a different audience and revoke one without disturbing the others. Access and content sharing.
New Password groups. A protected workspace can define several named user groups, each with its own password, instead of one shared secret for everybody. Password-protected visibility is a Premium and Enterprise feature.
New Rules scoped to specific collections. Any private link or password group can be limited to the collections you choose, so an internal runbook and a customer-facing guide can live in one workspace and reach different people. Collection-scoped access needs Pro or above.
One workspace, several audiences
Scoping is what lets you stop maintaining a second workspace just to hide a handful of pages. The sidebar and search results are filtered to the collections a reader's rule allows, so a restricted reader never sees a link they cannot open.
Performance and fixes
- Fixed Revoking a private link now takes effect immediately for readers who already had the page open, rather than at the end of their session.
- Fixed Restricted readers no longer see collections they cannot open listed in the sidebar or returned in search results.
- Perf Access rules are evaluated once per request instead of per page in the sidebar, which is what made large protected workspaces slow to render.
