Settings areas
| Area | What it controls |
|---|---|
| General | Workspace name and basic configuration. |
| Members | User access and roles. |
| Providers | AI provider credentials and available models. |
| API keys | Application and automation authentication. |
| Billing | Plan, limits, usage, and billing portal access. |
| Security | Enterprise security controls when enabled. |
Providers
Configure provider credentials once at the workspace level, then expose the approved models to projects. This keeps provider secrets out of prompt content, traces, and application code. Provider setup affects:- Prompt playground runs.
- Prompt evaluations.
- Continuous evaluation.
- Improve cycles and generated evaluators.
- Deployed prompt execution when your runtime uses Adaline-managed provider routing.
Members and access
Review workspace membership regularly. Give users the minimum role they need, and remove access when a user no longer works on the workspace. Members can appear in Improve notification pickers and audit context, so keep display names and access current.API keys and usage
API keys authenticate applications, SDK integrations, proxy traffic, deployment reads, logging, evaluation, and automation. Store keys in your application secret manager, rotate them when ownership changes, and never paste keys into prompts, traces, tickets, or docs. Usage and billing pages help admins understand limits for logs, evaluations, datasets, deployment reads, and Improve-related work.Operational setup
Before a project goes to production, admins should confirm:- Provider credentials are configured and tested.
- API keys are stored in the application secret manager.
- Billing and usage limits are understood.
- Security and data-retention policies match the team requirement.
- Production prompts have deployment environments configured.
- Webhooks or CI/CD automation are ready if downstream systems cache deployments.