Sep 11
Show a sign-in or request-access entry for restricted collections
When a collection is restricted inside an otherwise public help center, keep an optional visible entry explaining that the documentation exists and requires access. Give visitors a clear sign-in or request-access action instead of only removing the collection from navigation. Do not reveal protected article content or grant access automatically. Support teams need to keep general documentation public while directing eligible readers to restricted product documentation.
Pending
Clarification from the customer: their docs platform cannot password-protect anything, so they run two sites, one public and one behind a shared password, purely to gate an Apps section. What they want is the restricted section to stay listed in the public help center, with the sign-in prompt appearing when a reader opens it, and an option to point readers at their own intake form (theirs posts to Slack) rather than a built-in request-access queue. The workaround of a public placeholder article linking to the locked section does not fit, because readers who are already signed in would still see the placeholder.