Organizations

Keep a team's localization resources and authority together, and configure the settings that affect its callers.

An organization owns localization engines, shared guidance, integrations, and work. Your account joins it through membership. Signing in identifies you; the selected organization determines which resources and permissions are involved.

Create an organization when the work needs a distinct owner, or accept an invitation to join the existing team. Before configuring resources, inviting colleagues, or buying credits, confirm the selection. Use the organization ID in automation records and investigations when similar names could be confused.

Configure general settings #

General settings include the organization's name and timezone. Changing them requires org:manage_settings. Organization deletion has the separate org:delete permission.

Use a recognizable name and the timezone appropriate for applicable reports. When comparing periods, retain the report's actual range and timezone. Renaming the organization or changing its timezone does not change translation terminology, voice, or models.

Select the engine for each workflow #

API translation jobs require an explicit engineId. The CLI stores the organization and engine selected through lingo link; integrations have their own saved selection. Confirm those IDs when moving a workflow between organizations or changing its translation policy.

Changing organization settings does not grant a caller access to the chosen engine. Check the credential and engine scope independently through API keys.

Keep resource and membership changes distinct #

Team covers invitations, removal, and ownership transfer. Roles and permissions covers authority. Localization engines covers model, guidance, and pipeline settings.

Changing an organization name does not move a service key to another organization. Creating another organization does not transfer localization engines or their attachments. Check the owning IDs when changing a caller's organization.

Leaving ends your participation; deleting the organization removes the wider ownership boundary and its resources. Ensure another Owner remains before leaving or stepping down, and use deletion only when that broader outcome is intended.