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.

On Business and Enterprise plans, DeepReference becomes a team workspace. An admin creates member accounts, shares language assets with them, and manages API access, so the whole team translates with the same terminology, the same memory, and the same rules.

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).
• Per-member permissions: each member can individually be allowed to share assets, edit shared assets, or delete them. Admins have all three; everyone else gets exactly what you grant.
• 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: glossaries, termbases, and translation memory shared across the team, so member work reinforces the same assets instead of fragmenting them. Shares can be revoked at any time, and members see a "shared with me" list.
• 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

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.