This is part 3 of the full wxrks permission-by-permission reference, organized by category to match the tabs on a user's Permissions page. For the four roles and how permissions work, see All about wxrks roles. Part 1 covers Account through Organizational Unit, part 2 covers Permission Group through Search: see wxrks Permissions Reference: Account to Organizational Unit and wxrks Permissions Reference: Permission Group to Search.
Roles: AA = Account Admin, PM = Project Manager, CL = Client, VE = Vendor. A "No" means the role does not inherit the permission automatically — but an Account Admin can still grant it individually (unless noted otherwise).
Task
Permission | Description | AA | PM | CL | VE |
Auto-Assign Tasks | Ability to auto-assign tasks, for example in the autopilot context | Yes | Yes | No | Yes |
Bulk Delivery Tasks (Outside Editor) | Allows you to deliver tasks in bulk without opening the Editor | Yes | No | No | No |
Confirm All Segments (Outside Editor) | Allows confirming all segments without opening the Editor | Yes | No | No | No |
Confirm Vendor Work Hours | Allows users to confirm the number of hours worked by a vendor, ensuring accurate tracking and payment | Yes | Yes | No | No |
Recalculate Task Budget | Allows the user to recalculate task budget based on the linguist current rate | Yes | Yes | No | No |
Reject Assignment | Allows users to reject a task assignment | Yes | No | No | No |
Task Assign | Ability to assign tasks to a user | Yes | Yes | No | No |
Task List | Ability to list tasks | Yes | Yes | No | Yes |
Task Pending Acceptance | Allows vendors to accept or reject manually assigned tasks that require pending acceptance | Yes | Yes | No | No |
Task Retrieve | Ability to retrieve a single task | Yes | Yes | No | Yes |
Task Update | Allows for the maintenance of attributes in tasks, such as due date and instructions | Yes | Yes | No | Yes |
In practice:
Auto-Assign Tasks — In the Project Overview tab, shows an Auto-assign section with configuration and a trigger button. Auto-assignment matches tasks to linguists based on configured rules (language pair, expertise, availability). Without this permission, the auto-assign section is hidden and tasks can only be assigned manually.
Task Pending Acceptance — In the Vendor home page, shows a Pending Acceptance tab with a count badge for tasks that have been manually assigned but require the vendor to explicitly accept or reject them before starting work. Without it, the tab is not visible and vendors cannot be required to confirm assignments.
Bulk Delivery Tasks (Outside Editor) — In the vendor task list, enables a Bulk Delivery action at the task group level to deliver multiple tasks at once without opening the Editor for each one. Without it, tasks must be delivered individually.
Confirm All Segments (Outside Editor) — Enables a Confirm All Segments action directly from the task list, without needing to open the Editor. This is useful for tasks where the content has been reviewed externally and only needs to be marked as confirmed. Different from Confirm All Segments (In Editor), which requires the Editor to be open.
Confirm Vendor Work Hours — Shows a confirmation button and modal for a Project Manager to confirm the number of hours a vendor reported working on a task. This is part of the timesheet reconciliation workflow and feeds into payables calculation. Without it, the hour confirmation modal and button are not accessible.
Recalculate Task Budget — Shows a Recalculate Budget button in the task's payment details modal. Triggers a recalculation of the task cost based on the linguist's current configured rate, rather than the rate that was in effect at the time of assignment. Without it, the recalculate button is hidden and the budget is locked at the original calculated value.
Reject Assignment — Allows a vendor to reject a task that has been assigned to them, sending it back to an unassigned state. Shows a Reject Assignment option in the task dropdown menu. Without it, vendors cannot decline tasks assigned to them.
Terminology Kanban
Permission | Description | AA | PM | CL | VE |
Kanban Add Terms | Allow add terms in a kanban board | Yes | Yes | No | Yes |
Kanban Approve Terms | Allow users to approve terms in a kanban board | Yes | Yes | No | No |
Kanban Bulk Move Terms | Allow users to bulk move terms between lanes in a kanban board | Yes | Yes | No | No |
Kanban Create Board | Allow users to create kanban boards | Yes | No | No | No |
Kanban Delete Board | Allow users to delete kanban boards | Yes | No | No | No |
Kanban Ignore Language Pair Restriction | When granted, shows all Kanban board entries; otherwise, restricts entries to those matching the language pairs of the user | Yes | Yes | No | No |
Kanban List Terms | Allow users to list kanban terms | Yes | Yes | No | No |
Kanban List Terms Reviews | Allow users to list kanban terms reviews | Yes | Yes | No | No |
Kanban Move Terms | Allow users to move terms between lanes in a kanban board | Yes | Yes | No | No |
Kanban Reject Terms | Allow users to reject terms in a kanban board | Yes | Yes | No | No |
Kanban Retrieve User Metadata | Allows retrieval of metadata for users who have performed actions on terms within the Kanban board | Yes | Yes | No | No |
Kanban Update Board | Allow users to update kanban boards | Yes | No | No | No |
Kanban Update Request Type | Allow users to update terms request type | Yes | No | No | No |
Kanban Update Terms | Allow users to update kanban terms | Yes | Yes | No | No |
In practice:
Kanban Ignore Language Pair Restriction — By default, the Terminology Kanban board only shows terms that match the language pairs configured for the user. With this permission, that filter is removed and the user sees all terms across all language pairs on the board. Without it, a Project Manager or linguist only sees terms relevant to their assigned language combinations.
Kanban Retrieve User Metadata — In the Kanban board, each term card can show metadata about which user performed an action on it (e.g., who approved or rejected a term). With this permission, that attribution information is visible. Without it, actions are recorded but the user identity is not displayed on the cards.
Kanban List Terms Reviews — Controls whether the user can see the review history/comments associated with terminology Kanban entries. Without it, review data is not accessible in the board.
Kanban Add Terms — Shows the button to submit new terminology candidates to the Kanban board directly from the Editor (via the glossary tooltip) or from the Terminology section. Vendors with this permission can contribute terminology suggestions.
Timesheet
Permission | Description | AA | PM | CL | VE |
Delete Timesheet | Allows deleting timesheet entries | Yes | Yes | No | No |
Edit Timesheet | Allows creating and editing timesheet entries | Yes | Yes | No | No |
Edit User Rate | Allows editing hourly rates | Yes | No | No | No |
Export Timesheet | Allows exporting timesheet entries | Yes | No | No | No |
View Timesheet | Allows viewing timesheet entries | Yes | Yes | No | No |
View Timesheet Profitability | Allows viewing project profitability including timesheet rates | Yes | No | No | No |
View User Rate | Allows viewing hourly rates | Yes | No | No | No |
In practice:
View Timesheet — The master gate for the entire Timesheet section. Without it, the Timesheet navigation item and all timesheet data are not visible. All other Timesheet permissions require this one to be enabled first.
Edit Timesheet — Controls whether the user can add new timesheet entries and modify existing ones. Without it, the Add row button is hidden and existing entries are read-only.
Delete Timesheet — Shows a delete action on individual timesheet rows. Without it, entries cannot be removed.
Export Timesheet — Shows the Export button in the Timesheet management view, allowing the user to download timesheet entries as a file. Without it, the export button is hidden.
View Timesheet Profitability — Shows a profitability metrics section in the task card and task overview, combining revenue and cost data including timesheet rates. Without it, profitability information is hidden even if the user can view the timesheet itself.
View User Rate — In the User Languages tab, shows the configured hourly rate for Project Manager users. Without it, rates are not displayed to the viewer.
Edit User Rate — In the User Timesheet Info section, enables the currency and hourly rate input fields. Without it, rate fields are hidden and rates cannot be configured or changed.
Translation Memory
Permission | Description | AA | PM | CL | VE |
TM Clear | Ability to clear a Translation Memory | Yes | No | No | No |
TM Create | Ability to create a new Translation Memory | Yes | Yes | No | No |
TM Delete | Ability to delete a Translation Memory | Yes | No | No | No |
TM Export | Ability to export a Translation Memory | Yes | Yes | No | No |
TM List | Ability to list Translation Memories | Yes | Yes | No | No |
TM Retrieve | Ability to retrieve a Translation Memory | Yes | Yes | No | No |
TM Segments Import | Ability to import segments to a Translation Memory | Yes | Yes | No | No |
TM Update | Ability to update a Translation Memory | Yes | Yes | No | No |
In practice:
TM Clear — Permanently removes all translation segments stored inside a Translation Memory, without deleting the TM record itself. This is a destructive, irreversible action and is restricted to Account Admins.
TM Segments Import — Controls whether the user can upload a TMX, XLIFF, or similar file to bulk-import segments into an existing Translation Memory. Without it, the import option is not available.
TM Export — Controls whether the user can download the Translation Memory contents as a TMX file for use in other tools or as a backup.
User
Permission | Description | AA | PM | CL | VE |
Can create/update Taxes (Payables) | Grants the ability to create or update taxes for Payables | Yes | No | No | No |
Edit Custom Fields | Allows the user to edit existing custom fields | Yes | No | No | No |
User Analytics Access | Allows the user to access the wxrks Analytics Tool | Yes | No | No | No |
User API Token | Allows user to manage their own API token | Yes | No | No | No |
User Can Disable Augmented Translation Actions | Allows the user to disable the Augmented Translation Actions in the Editor | Yes | Yes | No | Yes |
User Can Enable Augmented Translation Actions | Allows the user to enable the Augmented Translation Actions in the Editor | Yes | Yes | No | No |
User Delete | Allows user deletion | Yes | No | No | No |
User List | Ability to list users | Yes | Yes | No | No |
User List eligible linguists | Ability to list eligible linguists | Yes | Yes | No | No |
User Reset Password | Allows to reset a user's password | Yes | No | No | No |
User Retrieve | Ability to retrieve a single user | Yes | Yes | No | No |
User Save | Ability to create a new user or update an existing one | Yes | Yes | No | No |
User Select Org Unit in Portal | Allows the user to select an organizational unit in the portal, and override the default account | Yes | No | No | No |
User TMS Access | Allows the user to access the wxrks TMS | Yes | Yes | Yes | Yes |
User Update Billing | Ability to update a user's billing information | Yes | No | No | No |
User Update Payment | Ability to update a user's payment information | Yes | No | No | Yes |
User Update Roles | Manage the roles of a user | Yes | Yes | No | No |
In practice:
User TMS Access — This is the master gate to the entire wxrks TMS. Without it, a non-admin user attempting to log in immediately receives an alert "You don't have permission to access TMS" and is redirected to the login page. Every user who needs to work in the platform — whether as a linguist, project manager, or client — must have this permission enabled. It is inherited by all four roles and can be individually disabled by Account Admins for specific users.
User Select Org Unit in Portal — In the Translation Portal (
/portal), users with this permission see a modal in the upper area of the screen to select which organizational unit they want to work under, overriding the account default. Without it, the org unit selector modal does not appear and the portal always uses the account's default organizational unit.User API Token — In My Account → Security, shows a section where the user can generate and manage their personal API token for integrating with the wxrks API. Without this permission, the token generation button is disabled.
User Analytics Access — Controls access to the wxrks Analytics tool. Without it, the analytics section is not accessible to the user.
Edit Custom Fields — Controls whether the user can click the Edit button on custom fields attached to user profiles and other records. Without it, custom fields are visible but read-only.
User Delete — Shows a Delete option in the user actions dropdown (visible to Account Admins managing other users). Without it, users can be deactivated or have their access removed, but cannot be permanently deleted.
User Can Disable Augmented Translation Actions / User Can Enable Augmented Translation Actions — Augmented Translation (AI-assisted suggestions, such as machine translation pre-fills) can be toggled on or off in the Editor. The Disable permission allows the user to turn it off for themselves; the Enable permission allows them to turn it back on. Granting the Disable permission without the Enable permission means the user can turn off Augmented Translation but cannot re-enable it without admin intervention.
User Update Billing — Controls access to editing billing information (e.g., billing address, invoice details) in a user's profile. This is used for account-level billing management.
User Update Payment — Controls access to editing payment information (e.g., bank account details, payment method) in a user's profile. Vendors typically need this to set up how they receive payables.
Can create/update Taxes (Payables) — Allows configuring tax rates that apply to Payables at the user level. Without it, tax configuration fields for payables are not accessible.
Quick reference
Role | Inherits by default |
Account Admin | Full management of the account: users, seats, permissions, organizations, org units, price lists, accounting (payables, receivables, payouts), connectors, projects, tasks, timesheets, TMs, glossaries, terminology boards, quality, and the Editor |
Project Manager | Day-to-day project operations: create and manage projects, assign tasks, manage TMs and glossaries, work in the Editor, sync and deliver connector projects, view quality data, and manage timesheets |
Client | Requesting and following projects: create projects, upload/download files, approve projects, change project status, run auto-translation, and manage their organizations and organizational units |
Vendor | Executing translation work: open the Editor, search glossary terms, update TMs, list and update their tasks, view their payables, work with review/PDF preview files, and manage their own payment information |
Troubleshooting
A toggle is locked and cannot be changed — the permission is inherited from the user's role, a Permission Group, an Organization, or an Organizational Unit. Account Admins can disable only the inherited permissions listed in the overview section above; the rest stay enabled while the user has the role.
A user lost access after a role change — permissions inherited from the old role are removed automatically. Re-grant individual permissions on the Permissions tab if needed.
A user has unexpected access — check whether the user has multiple roles or belongs to a Permission Group; both add permissions on top of individual grants.
A user cannot add glossary terms — see the troubleshooting steps in the Glossary section of Part 1.
A user cannot log in and sees "You don't have permission to access TMS" — the User TMS Access permission has been disabled for that user. Re-enable the toggle on their Permissions tab.
Related articles
All about wxrks roles — the four roles and how inherited/granted permissions work.
How to manage user information — every other tab on a user's profile: contact details, billing, associations, autopilot, tags, and metrics.
How to manage Permission Groups — grant the same set of permissions to several users at once.
All about Organizations and All about Organizational Units — every tab and setting these two entities have.
