Identity & access
Every request answers three questions: who is acting, whose credentials the call uses, and who can see the result.
A member is a person or agent in your organization. An end user is
your customer’s user; Introspection stores each one as a customer member.
Who is acting
| Who | Member type | How they get in | Page |
|---|---|---|---|
| A teammate | business, role owner, admin, or member | Dashboard or introspection login | Projects & members |
| The agent | agent: Member Agent (default) or Admin Agent | The API credential or application it is linked to | How agents act |
| An end user | customer, keyed user:{id}, anon:{id}, <idp>:<sub>, or an Introspection account ID | Your backend names them, or an application signs them in | Sign-in for your users |
| A backend or script | Not a member: an API key or service account acting as an agent member | Bearer token | Credentials |
Who owns a task, and whose memory it uses, is in Run a task for an end user.
Whose credentials a tool call uses
The agent never holds a real secret. Introspection adds the credential as the request leaves the sandbox.
| The agent calls | Credential | Configure in |
|---|---|---|
| A model provider | Introspection’s key, or your key on a byok runtime | Choose and change models |
| An API or MCP server with a shared token | A write-only credential | Bindings |
| A provider account through an OAuth connector | The end user’s user connection, else the connector’s shared connection | Per-user tool access |
| A partner that must know the end user | A short-lived JWT signed by your application | Tell a partner who the end user is |
| GitHub | A short-lived token for the granted repositories | Repositories |
Who can see what
| Resource | Who sees it | How to widen it |
|---|---|---|
| Projects | Every member of the organization | Not configurable |
| Runtimes, recipes, bindings, judges, experiments | Everyone in the project | Not configurable |
| Conversations, tasks, files, memory | The owner, plus organization owners and admins | A share; a task is also visible to members whose tags match its tags |
| Datasets (annotations) | Annotations on conversations you can see, plus conversations assigned to you | Share the conversation |
| Anything, from a session acting for an end user | Only that end user’s work plus shares, even as the Admin Agent | A share |
Choose how your app authenticates
| Method | Who proves the end user | Use it for |
|---|---|---|
| API key | Your backend names them (optional) | Trusted servers, scripts, CI |
| Service account | Your backend names them | Short-lived tokens, browser token brokers |
| Federated application | Your identity provider | Introspection must verify each end user, on the web or in a native app |
| Hosted login | Your identity provider, through an Introspection login page | A browser app with no login page of its own |
| Native app | A code Introspection emails | Native apps without their own sign-in |
Every API key and application belongs to one project and one environment.
Next
Last updated on