Customer admin and settings

Who this is for

This guide is for customer admins and project owners who manage how their organisation uses Kaidera. It explains configuration at a functional level, not internal administration.

Organisation settings

Organisation settings describe the customer account: company profile, account owner, plan, billing route, support route, security expectations, and defaults that apply across projects.

People and roles

Admins should be able to invite users, assign roles, group users into teams, review permissions, and remove access when someone no longer needs it.

• Use least privilege for sensitive projects.
• Keep approver roles clear.
• Review access when project ownership changes.

Security settings

Security settings can include MFA expectations, SSO where available, device or token controls, support access rules, and audit visibility.

Model and provider settings

Admins decide which providers, models, model groups, and fallback rules are available to users and AI workers. Public docs should explain the effect of those controls without exposing credentials.

Usage and limits

Admins should understand credits, quotas, rate limits, usage by project or model, and what happens when plan limits are reached.

What can go wrong

Admin issues usually come from unclear owners, broad permissions, outdated user access, provider configuration gaps, or missing billing/usage expectations.

Read next

Read Billing and usage for commercial controls, Provider setup and BYOK for model access, and Trust and security for enterprise controls.