Skip to main content
Not every piece of documentation is meant for every reader. Nulix Audiences let you define named groups of readers and then attach those groups to specific articles or categories, so only the right people see the right content. Whether you want to hide beta features from general users, surface internal runbooks only to your team, or give enterprise customers access to advanced guides, Audiences give you that control — without maintaining separate knowledge bases.

​
What Is an Audience?

An audience is a named label that represents a segment of your readers. You create audiences in your workspace settings and then assign them to content. A reader belongs to one or more audiences based on attributes you pass to Nulix (typically via your app or the Nulix API). Nulix includes a built-in “All Users” audience that covers every authenticated visitor. You can create as many custom audiences as your plan allows.

​
Example Audiences

​
Restricting Articles and Categories

You can assign an audience to any article or category directly from the editor sidebar:
1

Open the content item

Navigate to the article or category you want to restrict inside your knowledge base editor.
2

Open Visibility settings

In the right-hand panel, click Visibility & Access to expand the audience controls.
3

Select an audience

Choose one or more audiences from the dropdown. Only readers who belong to at least one of the selected audiences will see this content.
4

Save and publish

Save your changes. The restriction takes effect immediately for published content and at the time of publishing for drafts.
When you restrict a category, all articles nested inside it inherit the same audience restriction automatically. You can tighten restrictions on individual articles within the category, but you cannot make a child article visible to a broader audience than its parent category allows.

​
Passing Audience Membership via the API

Nulix integrates with your product’s identity layer so that audience membership is determined at runtime, not manually managed inside Nulix. When a reader authenticates in your app, you generate a signed viewer token that includes the audiences the reader belongs to. Pass this token to the Nulix embedded widget or public API, and Nulix automatically filters content to match their membership. A minimal token payload looks like this:
Sign the token with your workspace’s secret key and pass it in the Authorization header or as a query parameter when loading the knowledge base. Nulix validates the signature and resolves the reader’s visible content in real time.
Never expose your workspace secret key in client-side code. Always generate viewer tokens on your backend server and send only the signed token to the browser.

​
Use Cases

Tiered Documentation

Show basic guides to Free users and unlock advanced content for Pro and Enterprise customers automatically.

Internal-Only Articles

Publish internal SOPs, runbooks, or admin guides in the same knowledge base without exposing them to external readers.

Beta Feature Docs

Document features in active development and restrict visibility to enrolled beta testers until general availability.

API Integration

Connect your app’s identity provider to Nulix so audience membership is resolved automatically from your user attributes.

​
Public vs. Gated Content

Content that has no audience restriction (or is assigned to “All Users”) is visible to every reader, including unauthenticated visitors if your knowledge base is set to Public. As soon as you assign a non-default audience to a piece of content, Nulix requires the reader to be authenticated and carry the matching audience claim in their token before rendering that content.

​
Next Steps

Visibility & Access

Explore the full range of visibility controls available for articles, categories, and entire knowledge bases.

API Access

Learn how to authenticate readers and pass audience membership programmatically using the Nulix API.