LingoHub provides secure team management through a flexible, two-level role hierarchy. Roles ensure that team members access only the permitted parts of your Workspace and Projects, keeping your data secure and your workflows organized.
Instead of configuring dozens of individual permissions for every user, permissions are bundled into standard roles. This article explains the difference between Workspace and Project levels, the specific permissions for each role, and how seat types affect your available roles.
Two-level role hierarchy
You can manage access independently at both the Workspace and Project level. This allows for granular control; for example, a user can be a Member of the Workspace (with no global access) and an Admin of a specific Project at the same time (obtaining more permissions).
Workspace roles: Control high-level access to the entire organization, including billing and global settings.
Project roles: Control access within specific projects. These roles define who can upload files, manage settings, or delete the project.
Within a Project, you can further restrict access by assigning members to specific languages only.
Note: If you update a user’s role at any time, their access permissions will be updated immediately across the platform.
Workspace roles - Workspace permissions
Workspace roles and their respective permissions apply to global settings and assets across your entire organization.
Category | Description | Owner | Admin | Localization Manager | Member |
Workspace & billing | Manage billing, invoices, and global settings. | ✅ | ❌ | ❌ | ❌ |
Administration: Members | Invite, remove, or change team members' roles. | ✅ | ✅ | ❌ | ❌ |
Administration: Plugins & API | Manage integrations and connected third-party applications. | ✅ | ✅ | ❌ | ❌ |
Administration: Logs | Access and review security and activity logs. | ✅ | ✅ | ❌ | ❌ |
Administration: API Access | Create, manage, and view API keys. | ✅ | ✅ | ❌ | ❌ |
Administration: Projects | Create and delete translation projects within the Workspace. | ✅ | ✅ | ❌ | ❌ |
Translation orders | Create and manage professional translation orders via the Marketplace. | ✅ | ✅ | ✅ | ❌ |
Cost reports | Access detailed financial reports and translation cost breakdowns. | ✅ | ✅ | ✅ | ❌ |
Work reports | Monitor team productivity and translation progress reports. | ✅ | ✅ | ✅ | ❌ |
Text tools | Manage Style Guides, Glossaries, and Translation Memories. | ✅ | ✅ | ✅ | ❌ |
Workspace roles - Project permissions
Workspace roles and their respective permissions apply to global settings and assets across your entire organization.
Category | Description | Owner | Admin | Localization Manager | Member |
General: Languages | Add, remove, or manage the target languages within the project. | ✅ | ✅ | ✅ | ❌ |
General: Settings | Modify project-specific metadata, resource settings, and delete projects. | ✅ | ✅ | ❌ | ❌ |
General: Activities | Access the project's activity stream to monitor updates and history. | ✅ | ✅ | ✅ | ❌ |
General: Resources | Manage project assets and access file upload/download features. | ✅ | ✅ | ✅ | ❌ |
General: Context Images | Upload and assign screenshots to provide visual context for translators. | ✅ | ✅ | ✅ | ❌ |
Segments: General | Manage high-level segment settings such as "translatable" and plural status. | ✅ | ✅ | ✅ | ❌ |
Segments: Keys | Create, edit, and manage unique translation keys for the project. | ✅ | ✅ | ✅ | ❌ |
Segments: Texts | The ability to translate and edit the actual segment content. | ✅ | ✅ | ✅ | ❌ |
Project roles - Project permissions
Project roles define what a user can do inside a specific translation project.
Category | Description | Admin | Localization Manager | Translator |
General: Languages | Add, remove, or manage the target languages within the project. | ✅ | ✅ | 👀 |
General: Settings | Modify project-specific metadata, resource settings, and delete projects. | ✅ | ❌ | ❌ |
General: Activities | Access the project's activity stream to monitor updates and history. | ✅ | ✅ | ❌ |
General: Resources | Manage project assets and access file upload/download features. | ✅ | ✅ | 👀 |
General: Context Images | Upload and assign screenshots to provide visual context for translators. | ✅ | ✅ | ❌ |
Segments: General | Manage high-level segment settings such as "translatable" and plural status. | ✅ | ✅ | 👀 |
Segments: Keys | Create, edit, and manage unique translation keys for the project. | ✅ | ✅ | 👀 |
Segments: Texts | The ability to translate and edit the actual segment content. | ✅ | ✅ | 👀 |
In the tables above, we use the following indicators to define the depth of access:
✅ Full access: The user can view, edit, create, and delete items in this category.
👀 View only: The item can be viewed but not modified.
❌ No access: This category and its data are completely hidden from the user.
Note: The Member role shows ❌ for most actions. This is because a Workspace Member gains additional permissions when assigned a specific role (e.g., Translator) within a Project.
Language-specific roles (Translators)
For the highest level of precision, you can restrict a user's access to specific languages within a project. When assigning a user to a language, you choose between two levels:
Translate: Allows the user to edit and save translations for that language only.
Manage: Gives the user full control over that specific language, including managing statuses and language-specific settings.
Understanding seat types and billing
To simplify how seats are counted and ensure you can add as many collaborators as needed, LingoHub uses two distinct seat types:
Standard seats (Unlimited): These include the Member and Translator roles. You can add an unlimited number of these collaborators across any plan.
Advanced seats (Plan-limited): These include management roles such as Owner, Admin, and Localization Manager, as well as any Custom Roles. The number of available Advanced Seats depends on your specific plan.
Note: Custom Roles offer tailored flexibility for your unique workflows and are available on Pro plans and above.
Awesome! You have finished the article on roles and permissions. We hope that it helped you find answers to all your questions. Otherwise, contact our support, and we will gladly help!