Show content to specific readers
Show different content to different readers: a plan's features only to customers on that plan, partner docs only to partners, internal notes only to your AI agent. Readers are grouped by details your product sends when they sign in, and each section, collection and article decides who can read it.
User groups and limited content are on Pro and Enterprise. Owners and admins can change this.
Who can read it
Set the audience on a section or collection from its Access tab, and on an article in its settings. Each level can only narrow the one above it.
Inherit: the same readers as the level above. This is the default.
Signed-in readers (on an article, Anyone signed in): anyone with a help center account.
Specific groups (on an article, Specific user groups): only readers in the groups you pick.
For a section or collection, also choose what everyone else sees: Show with a lock lists the title with your message and a sign-in button, and Hide leaves it out entirely. An article limited on its own is always hidden from readers who can't open it. Search engines and AI crawlers never get limited content.
An API reference has no audience of its own. It follows its section, so put it in a section limited to the right group. See Publish an API reference.
Where an article is listed
Separately from who can read it, Listed in decides where an article shows up:
Setting | Sidebar | Search and your AI agent |
|---|---|---|
Everywhere (default) | Yes | Yes |
Unlisted | No | Yes |
Hidden | No, direct link only | No |
AI assistant only | No, and readers can't open it | Only your AI agent uses it |
Build groups from reader properties
A group is a rule on reader properties, such as plan is enterprise. Readers join and leave groups on their own as their properties change. Create groups in Help Center > Access Control > Groups. A reader must match every condition in a rule.
Properties come from your product when readers sign in with it or with OIDC. A developer sets that up: see Sign readers in with JWT or OIDC. You can also edit a reader's properties by hand in the Users tab, but their next sign-in through your product replaces them.
How rules match:
Lists: when a property is a list, such as
modules: ["csrd", "esg"], is and contains both match if any item equals the value. is any of matches if any item equals any of your values.Text: contains matches part of the text. is needs the whole value. Both are case sensitive.
Nested properties: match them with a dot, such as
frameworks.csrd.Yes or no, and numbers: the value
trueor25matches a property sent as true or as the number 25.
A reader signed in with the shared password has no properties, so groups never apply to them.
What your AI agent knows about each reader
Your AI agent only answers from content the signed-in reader can read. It also sees the names of the reader's groups, and when the widget signed them in, their name, email and properties. It uses these when they bear on the question and doesn't recite them back. Name groups the way you'd describe them to a customer, such as "CSRD module", because the agent may use the name in an answer.