Administration

Set up the organization, give people and services appropriate access, and manage the usage they create.

An organization keeps the team's localization resources, members, credentials, and billing together. Your personal account can belong to several organizations, so selecting the organization determines which work and authority you are using.

Administration helps that access follow real responsibility: a colleague needs the resources for their job, an automated service needs a credential that can outlast its creator, and the account owner needs to understand and pay for usage.

Establish the team and its authority #

Organizations covers creating, joining, switching, and configuring an organization. Team follows a colleague through invitation, membership changes, and ownership transfer. At least one Owner must remain so someone can continue managing the organization.

Roles and permissions explains how organization roles and resource grants combine. They add authority: a narrow grant does not cancel a broader role. Use that model when someone needs access to selected localization engines without responsibility for the whole account.

If a control is missing or an action is denied, Feature access separates plan entitlement, permission, and what the interface exposes. Each has a different remedy.

Give automation its own credential #

API keys covers creation, scope, rotation, and revocation. A personal key follows its creator's membership and permissions. An organization service key can have explicit roles and resource scope without depending on one member remaining on the team.

Store the secret in the caller's secret-management mechanism, then configure the tool that uses it: API authentication, CLI authentication, or MCP security. A credential establishes authority; the caller still needs to select the intended organization resources.

Account for usage and changes #

Billing explains plans, payments, credits, and automatic top-ups. Usage connects account spending with the work behind it, while distinguishing credits from provider tokens and individual request costs. BYOK runs a provider's models on your organization's own key, billed by that provider.

When an unexpected setting changes, Audit logs explains the recorded administrative evidence and its coverage. For what happened during translation, use request evidence. A record of who changed a setting and a record of which model generated a response answer different questions.

End access at the right scope #

A departing member, an obsolete credential, and an organization that is no longer needed require different actions. Remove membership through Team, revoke credentials through API keys, or follow Delete an organization when the whole organization should be removed. Review that action's consequences before using it to solve a narrower access problem.