Publish and control access
Publish a Help Center, set public or private visibility, and restrict private access by email domain.
The publish switch controls whether visitors can see the Help Center. Before you use this switch, review the title, the branding, the articles, and the navigation. Article status also matters. A published Help Center can contain draft articles. Draft articles are not for readers.
Treat a change in publication as a customer-facing release. After you save the change, verify the public route.
A Help Center can be public or private. If you select private access, allowed email domains control who can sign in. A visitor gives an email address. AgentStack sends one email that holds a 6-digit code and a sign-in link. Either one signs the visitor in, and the visitor can open the link on a second device. The code is valid for 15 minutes. Eight wrong codes lock that code out. A completed sign-in lasts 30 days. AgentStack also links the visitor to the help desk customer record that has the same address.
A listed domain must match the full domain of the address. A subdomain does not match a listed parent domain. Add mail.example.com as its own entry when you need it. AgentStack never tells the visitor which domains are allowed.
Warning: an organization member who has Help Center write access reads a private site without a code. Do not test the gate with your own workspace account. Sign out first, or use a private browser window, and sign in with an address from an allowed domain. A member who has only the publish permission or the delete permission does not get this bypass.
Two later changes end a visitor session. A change of visibility signs out every visitor of that site at once. Removal of a domain locks out its visitors on their next request. Plan both changes with the support team.
A domain restriction does not replace a review of article content. It is not a general-purpose SSO system for the organization.
Publishing a Help Center requires the Help Center publish permission. Deleting a Help Center requires the delete permission. Changes to access can affect active visitors. Coordinate access changes with the support and customer-success teams. If you use a custom domain, configure its routing on the Domains screen. Each hostname routes to only one surface.