Workspace and settings
Sign in to work inside your organization. The hosted app uses account authentication; the shared team-password login is a separate legacy mode enabled only with LEGACY_AUTH=1. API keys connect applications and do not replace a human account.
Use Settings to inspect model availability, test provider connections, review pricing, and check retention. Provider configuration is needed for model calls initiated by the panel, including analysis and Testing Lab. Your existing app can keep using its own model provider credentials.
The integration key and app control scope serve different purposes. App creation issues ingest and read scopes. The SDK’s composed-prompt endpoint also requires prompt scope; confirm that permission before relying on remote prompts.
Workspace API
| Method and route | Purpose |
|---|---|
| GET /api/auth/me | Read the signed-in user and organization context. |
| GET /api/settings | Read workspace settings. |
| GET /api/models | Inspect available models. |
| GET /api/org/retention | Check the retention policy for the organization. |