Security and teams
Teams and enterprise
Set up members, permissions, word limits, shared language assets, review access, and API keys on Business and Enterprise plans.
Business and Enterprise provide organization membership, resource sharing and administration. Use Projects to group documents, Share project to give a reviewer access to a file, and team resources to make selected language assets available for lookup. These are separate choices: file access does not expose personal libraries.
What teams get
- Member accounts: the account owner invites members from the enterprise settings (and can resend an invite that got lost in a spam folder).
- Member permissions: organization settings control member roles and resource-management permissions. The editor currently reads authorized shared TM and glossary entries; a Read & write label does not enable editor save-back to another member’s library.
- Per-member word limits: cap how much of the team allowance any member can use, so one busy month in one department doesn't starve the others.
- Usage overview: a live view of the whole organization's word consumption, member by member.
- Shared language assets: the organization catalog lists shared resources. Members explicitly select shared memories and glossaries in Editor resources. Language and domain filters restrict the entries returned. Raw extracted terminology sets are not an editor glossary until reviewed and promoted into one.
- Review workflow: segment comments and segment history connect translators and reviewers inside the editors.
- API users: admins create and manage API keys for programmatic access from company systems.
Setting up a team
Upgrade to Business or Enterprise
Use an account with active Business or Enterprise access. Check your account page for the current plan and available organization controls.
Create members in enterprise settings
Each member gets their own login under your plan's word allowance.
Set permissions and limits
Decide per member who may share, edit, or delete team assets, and set word caps where you want them. Defaults are conservative: new members can use assets, not manage them.
Share the assets that matter
Use Shared with the team in enterprise settings to create a resource share. Choose its scope and filters, then follow the team resources guide to select it in an editor. Shared lookup does not change the owner’s entries.
Running low near month-end? Admins can buy word top-ups (100k / 500k / 1M packs) without changing the plan.
Why shared assets need an owner
An administrator decides which glossaries, termbases, and Translation Memories are shared and who may change or delete them. This keeps client terminology available to the right members without giving every member control over the underlying assets.
Keep exploring
Use organization-shared memories and glossaries
Share a library with your organization, select it in an editor and understand access, filtering and save destinations.
Organize a multi-file review
Group existing documents by client, track approval progress and assign a reviewer across selected files.
Share a project for review
Hand over an unfinished review while retaining the document, translations and change history.
API overview and authentication
REST endpoints for Business and Enterprise accounts to translate text and read current word usage with API-key authentication.