Project-Level Personas
What this covers
Project-level personas restrict what the conversational agent can see across a project. They are different from model-level personas, which publish scoped catalogues for JDBC/XMLA and in-app querying. Use project-level personas when the agent serves several audiences from the same project and each audience should see a different subset of models, measures, or dimensions.
How they differ from model personas
| Aspect | Project-level persona | Model-level persona |
|---|---|---|
| Primary consumer | Conversational agent | Query router, JDBC, XMLA, Measure Query Panel |
| Scope | One project, many models | One model |
| Restricts | Models, measures, dimensions exposed to the agent context | Measures, dimensions, hierarchies, filters, row-security bypass, tag restrictions |
| Enforcement point | Agent context assembly and query validation | Gateway/query-router persona gate |
| Typical user | Tenant admin or data steward configuring agent audiences | Modeller publishing audience-specific catalogues |
How the agent uses a project persona
When a persona is selected in Agent Chat, the prompt builder filters model profiles before the LLM sees them. Excluded models and attributes are not described to the model. If a later query plan references excluded objects, validation rejects it before execution.
A persona contains one or more model scopes. If a model scope is absent, that model is hidden from the persona. If a model scope exists with empty measure or dimension lists, that axis is unrestricted for that model. Non-empty lists act as allow lists.
Recommended design
Create personas for audiences, not individuals: Finance, Operations, Partner Support, Executive Review. Start broad enough for the audience to answer its real questions, then narrow only where governance requires it. Keep descriptions explicit because the persona name becomes part of the user-facing chat context.
Example
A Finance persona can include the payments and settlements models, allow revenue/cost/margin measures, and include fiscal calendar dimensions. A Partner persona can include only shipment count and SLA measures while excluding customer identity dimensions and cost measures.