Skip to content
Locize
LoginRegister

User Management

Overview

User management in Locize allows you to invite and manage team members with fine-grained permissions for each project. You can control access by version, language, or feature, ensuring everyone has the right level of access.

User management video

Watch the user management video as part of our showcase/demo.

Inviting Users

On your project settings page, under the USERS tab, you can:

  • Invite team members to a specific project
  • Assign permissions for specific versions, languages, or features
  • Adapt permissions at any time (admin role required)
  • Create anonymous invitation links with predefined permissions to share with others

Learn also about Managing Multiple Projects with Collective Billing and User Inheritance — including how inherited users affect billing and how to optimize costs.

Role Permissions

Each user can be assigned one of the following roles:

  • Admin: Full access to all features and settings, including billing and user management.
  • Accountant: Responsible for billing and accounting tasks only.
  • Manager: All permissions except billing/accounting. Can be scoped to specific versions, languages, or namespaces.
  • User: Can work on translations. Can be scoped to specific versions, languages, or namespaces.
  • Publisher: Like the user role, but can also publish or overwrite versions. Overwriting requires permission to all languages and namespaces.

Note:

  • Scoping a permission to specific languages (excluding the reference language) removes the ability to add or remove keys.
  • Only admins (and partially managers) can change team permissions at any time.

Additional permission flags

For User and Publisher roles, two optional flags fine-tune what a team member can do:

  • Can review (canReview) — grants permission to participate in the review workflow, i.e. approve or reject other users' translations. When scoped to specific languages, reviewing is limited to those languages. Admins and managers can always review; accountants never can.
  • Translate only (translateOnly) — restricts the user to editing translation values. Deleting keys (and other key-level structural changes) is blocked. Useful for external translators who should not be able to alter your project's key structure.

These flags are visible on the user-edit form for users and publishers only — admin/manager/accountant roles don't expose them. The same flags are honoured by the MCP server for AI-assistant access.

SAML Single Sign-On (SSO)

You can enable SAML SSO to allow users to access Locize through your chosen identity provider (IDP) in your project settings.

You can configure it on the "USERS" tab:

Or you can configure it in the "PLAN, ADDONS, ..." tab

Setup steps:

  1. Upload your IDP's metadata file.
  2. Optionally define user attribute mappings.
  3. Enter the appropriate IDP endpoints.

Once configured, your users can log in via:

https://www.locize.app/login/{identifier}

  • SAML SSO integration will increase your monthly costs.
  • SSO users cannot use the InContext popup approach.
  • You must still invite individual users to your project(s). SSO users do not automatically receive project permissions.

Audit Log

Admins and managers can download a full audit log of security- and access-relevant changes inside a project. The log is available from the USERS tab of your project settings via the Download audit log action.

Recorded events include:

  • Team membership — user added, removed, role or permission changes.
  • Invitations — invitation created, updated, or deleted (personal and open invitations).
  • Project security settings — MFA enforcement enabled or disabled.
  • SSO / SAML provider settings — provider configuration created, updated, or deleted.
  • API keys — API key created or deleted.

Each entry records who performed the action, when, and the user or setting affected.

The audit log is a paid feature — see pricing for availability per plan.