Get the Access You Need¶
A sign-in proves your identity; it does not grant all Team or inference access. Ask your administrator for the exact missing capability:
| You need | Ask for |
|---|---|
| Develop with a model or tool | Team membership, permission to create your own virtual key, Team allowance and the key's operation/resource policy |
| Run backend code | An ordinary service account and service virtual key in the intended Team |
| Build a managed app | agent.edit and, for Preview, agent.test in its Team |
| Publish or change access | Appropriate deployment publication/access permissions |
| Use Chat | Inclusion in that deployment's Chat audience; technical Team roles are unnecessary |
| Inspect request/Trace metadata | Appropriate own-key access or Team observability.read |
| Inspect captured content/export | Separate observability.content.read / observability.export |
| Change finance constraints | The relevant budget permission, or exact manageable key-local cap authority |
Share the Team, resource and safe correlation/decision ID. Never share a key or private prompt merely to request access. A customer label, Session ID or Trace ID does not grant access. After the administrator changes current policy, retry one request; no restart or new key is needed unless your credential or membership instance changed.
See virtual keys, roles, and troubleshooting.