Audiences, roles and scopes
Home · Audiences, roles and scopes
Goal
Use this page to choose the right documentation path. It separates daily product usage, project administration, Azure/platform administration and support/audit diagnostics.
Who this page is for
| Profile | Use this page to |
|---|---|
| Business user | Find task-oriented pages without Azure internals |
| Project owner | Find project roles, governance, knowledge and integration pages |
| Azure or tenant administrator | Find deployment, AI provider, license, integration and update pages |
| Support or auditor | Find diagnostic, AI Log and traceability pages |
Documentation levels
| Level | Contains | Does not contain |
|---|---|---|
| End user | Steps, roles, expected results, common blockers | Azure variables, secrets, raw payloads or infrastructure details |
| Project owner | Members, roles, policies, categories and project integrations | Connector secrets or low-level auth details |
| Azure/platform admin | Marketplace, Entra, AI provider, licenses, integrations and updates | Daily business workflows |
| Support/audit | Run ID, Trace ID, effective provider, activity and symptoms | Secrets, keys or internal endpoints |
Recommended paths
| Role | Start with | Then |
|---|---|---|
| New user | Getting started | Interface, Dashboard, Active project |
| Contributor | Knowledge | Agents, Structured outputs, PM Documents |
| Project owner | Access control | Project workspace, Governance |
| Tenant admin | Azure and Entra administration | AI provider, Licenses and updates |
| Support | Support, audit and diagnostics | AI Log, FAQ |
Label convention
The documentation uses the business term first and keeps the exact UI label when useful, for example Add to knowledge, All projects or Effective AI Provider.
Security rule
Never include secrets, passwords, tokens, full sensitive payloads or unmasked customer data in support requests.