Permissions provide the ability of precise control within the team access. With permissions, you can set up to which part of the project the team members have no access, which they can view or edit.
The permissions are separated into six main categories - "Company," "Marketplace," "Members," "Translation tools," "Developer tools," and "Projects." Inside each, there are subpoints you can also manage.
Let's take a look at the permissions in detail.
Note: Permissions are part of the roles we described in this article.
Note: You can provide the permissions in the process of new adding new team members. Read here.
Each category can be fully closed for the user by choosing "No permission" against the category name. Also, you can provide full access to members by using "Full permission."
If you want to manage the subcategories, choose "Restricted permission." Then you will be able to select one of the three options - "No access," "View," or "Manage." The first one restricts any activities for users with selected data. Let's overview the remaining two. For some categories, both options exist - "View" and "Manage"; for some, only one.
The primary set allows control of main company data and settings - billing information, subscription management, and audit logs.
Permission | Manage | View |
Gives full access to control the Company's settings, including an avatar, title, URL management, and Company deleting. | not available | |
Provides permission to add or edit the billing information, payment method, and overview invoices. | Provides permission only to overview the billing, payment, and invoices' data. | |
Subscription | Allows to change the subscription plan and adjust usage quotas (e.g., for Machine Translation.) | not available |
not available | Gives the ability to review members' actions within the Company to track what happened, when, and by whom. |
Control the access to the Marketplace tools "Orders," "Transactions," "Contracts," and "Text edits."
Permission | Manage | View |
Provides the ability to create, manage and cancel Translation Orders. | Allow view of the translation orders. | |
The user can create, edit and delete contracts for external translators and automatically generate the transactions based on the contracts data. | The user can view active/inactive contracts and transactions. | |
not available | Provides the ability to access the text edits report and export the data. |
Management of the Company's members
Permission | Manage | View |
Gives full access to adding and deleting users, editing roles, and providing member custom permissions. | Gives access only to view the existing company members. |
Control the access translating tools - "Translation memories," "Term bases," "Style guide," and "Labels."
Permission | Manage | View |
Permission to create, edit, set up, delete, and export translation memories. | Permission to view the existing translation memories. | |
Permission to create, edit, set up, and delete term bases and import/export entries. | Permission to view the existing term bases. | |
Permission to create, edit and delete the style guides. | Permission to view the existing style guides. | |
Permission to create, edit and delete the labels. | Permission to view the existing labels. |
Manage access to the developers' tools.
Permission | Manage | View |
not available | Providing access to the API logs to control which API calls have been performed. | |
Allows to create, edit and delete the API keys (they are used to access the Lingohub API by assigning specific permissions). | Allows to view the existing API keys. |
Control the users' access within the project.
Permission | Manage | View |
Permission to manage the project data like description, project name, and transfer/delete the project. | not available | |
Containers | Allows to manage container, e.g., adding and renaming resource files of a repository. | Allows to view container's data. |
Upload | The permission to import containers (e.g., files) by uploading them via Web UI or API. | not available |
Download | The permission to export containers (e.g., files) by uploading them via Web UI or API. | not available |
Push | Allows to push the projects' content to the connected repository or third-party integrations (Zendesk, Figma, etc.) | not available |
Pull | Allows to pull the content to the project from the connected repository or third-party integrations (Zendesk, Figma, etc.) | not available |
Integrations | Gives access to set up and manage integrations and connect repositories and applications (Figma, Zendesk, etc.) | Gives access to view the active integrations. |
The user can manually create the context images or upload them automatically, assign the context images to the appropriate segment, and edit or delete them. | not available | |
Packages | Allows to create and update package settings and their versions. | Allows to view the existing packages. |
Segments information | Gives the ability to change segment information like description, label, and manage the segment settings (translatable, plural) or delete it. | Gives the ability to view segment information - description, label |
Languages | Provides permission to change the segment's texts (translate the segment.) | Provides permission to view the segment's texts. |
Language-specific permissions
There are two options to provide permission to change the segment's texts or statuses.
In the "Languages" row, you can select "Manage." As a result, the user will have access to all the languages in all accessible projects.
Click on "Add language specific permissions" and choose from the list the languages you want to give access to.
Also, to give you more flexibility, Lingohub provides custom project permissions so that you can create different accesses for different projects. To add the permission rules to the next project - click on "Add project permission" at the bottom of the page and choose the appropriate one.
Awesome! You have finished the article about permissions. We hope that it helped you find answers to all your questions. Otherwise, contact our support, and we will gladly help!