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

• Requires active Business or Enterprise access; the account page shows the current plan and organization controls.
• Each member gets their own login under the plan's word allowance.
• Per-member permissions decide who may share, edit or delete team assets, with optional word caps. Defaults are conservative: new members can use assets, not manage them.
• Assets are shared from Shared with the team in enterprise settings, with a scope and filters. See Team resources. Shared lookup does not change the owner's entries.

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.