Profiles
Every user is assigned one of three profiles when invited. Profiles are stable — you assign one at invite time and rarely change it. Each one corresponds to a persona you’ll recognize from your team.Contributor — the knowledge/operations persona
The owner of the knowledge over time. Day-to-day responsibilities:- Acts on production — adds sources, edits artifacts, reviews feedback.
- Maintains the knowledge so it stays accurate as the business changes.
- Follows the operational workflow — work the feedback queue, refresh stale sources, apply Clara’s suggestions.
- Takes interviews — can take interviews assigned to them to capture their expertise.
Technical user — the backend/pipeline persona
More comfortable with backend systems and the data pipeline. Day-to-day responsibilities:- Tweaks data pipeline parameters — parsing, chunking, indexing.
- Configures extractors, flows, and connectors for new source types.
- Maintains advanced API integrations for systems that don’t use MCP.
User — the end-user persona
Primarily consumes the knowledge store rather than building it. Day-to-day responsibilities:- Uses the Q&A side — asks questions in the playground or through an AI client.
- Runs tools the knowledge store exposes through MCP.
- Submits feedback when something is wrong.
Permissions
Permissions are named grants that extend or restrict what a profile can do. They can also be configured in the knowledge store settings page.DataReader
Can use Chat or Task with the AI agent and read sources. This is the baseline grant for anyone who consumes the knowledge store: asking questions in the playground, running tasks, and browsing source documents.Admin
Can modify knowledge and sources, and see everything that’s done inside the knowledge store. Admins manage the store’s content — editing artifacts, adding or removing sources — and have full visibility into all activity, including other users’ conversations and interviews.Interviewee
Can take interviews assigned to them. Interviewees have no access to knowledge store data: they don’t see sources, artifacts, or the playground — only the interviews they’ve been assigned.Profiles vs. permissions
- A profile is the persona you pick at invite time. It sets the baseline for what someone can do and rarely changes.
- A permission is a backend-controlled grant added on top for a specific capability — useful when a profile baseline doesn’t quite match what one person needs to do.
[email protected].
How to invite users
You need to be a Contributor (or higher) to invite users to a knowledge store.- Go to the knowledge store settings.
- Click the Users tab.
- Click Invite user.
- Enter the user’s email.
- Select their profile.
- Click Invite user.