Skip to content
localisyncDocs
Open panel

Roles and members

Each member has one role in a workspace. The same account may have different roles in other workspaces.

The following permissions apply to an active workspace:

Action Owner Admin Editor Viewer
View members and all projects Yes Yes Yes Yes
Rename the workspace Yes Yes No No
Invite Admin/Editor/Viewer Yes Yes No No
Manage pending invitations Yes Yes No No
Change/remove non-owner members Yes Yes No No
Create projects and manage languages Yes Yes No No
Read translations and content history Yes Yes Yes Yes
Create/rename keys and edit values/contracts Yes Yes Yes No
Archive/restore translation keys Yes Yes No No
Transfer ownership Yes No No No
Archive/restore the workspace Yes No No No
Leave the workspace Transfer first Yes Yes Yes

Editor and Viewer both have read-only access to project/team settings. Owner/Admin/Editor can create and rename translation keys, change ICU contracts and edit active-language values. Only Owner/Admin archive or restore keys. Viewer reads translation values and history. None of these roles grants platform administration.

Open the workspace’s Members page. Each row shows the account email and role. All current members can view this list; only Owner/Admin can manage members or view invitation management.

  1. As Owner/Admin, open Members.
  2. Select the new role for a non-owner member.
  3. Choose Change role and confirm after reviewing its effect.

Admin can manage other Admins and can reduce their own role. Losing management permission also revokes pending invitations created by that person. The updated permission applies to subsequent requests.

The Owner cannot be changed through ordinary role controls. Use ownership transfer.

Choose Remove for a non-owner member, review the confirmation and confirm. That account loses access to this workspace. Its account and memberships in other workspaces remain available.

A removed member needs a new invitation to rejoin. Archived workspaces retain read access and block member management; the Owner must restore the workspace first.

Owner/Admin/Editor can create tags, assign them to active keys and import into active projects. Owner/Admin alone rename/delete unused tags. Every member, including Viewer, can filter tags and export; archived projects remain exportable. Jobs and files are private to their creator and require current membership. See tags and file transfers.

Projects start with main. Use Current workspace / Current project / Current branch in the header; upper-level lists preserve these choices. Content menus use the selected branch, while project Settings stays shared. See navigation and the branch permission matrix.

Owner/Admin/Editor can prepare a release from an active branch; all members can inspect packages and reports. Only Owner/Admin manage distributions/read keys, publish, confirm Preview tests, promote or roll back. Editor can cancel/retry their own eligible builds. Pending work rechecks current permission before committing; after a publication decision commits, worker retries complete that same decision. See publishing.

Owners/Admins manage provider credentials, limits and all assistance jobs. Editors can use safe connection metadata and manage their own jobs, spending through the shared configured limits. Viewers cannot use assistance, but retain translation/history read access. See provider permissions.

Owners and Admins manage provider connections and file mappings, approve removals and send pull requests or merge requests. Editors can prepare and apply non-removing imports; Viewers can read results. Git authorization is rechecked before processing. See Git workflow and provider setup.

Owners and admins can restrict an Editor to explicit project/language writes and assign review permission separately. Existing Editors remain unrestricted until this setting changes. New projects and languages are not automatically added to restricted grants. All projects remain readable within current workspace membership. See reviews and knowledge sources.

Cookie preferences

Your choice applies to localisync.com and docs.localisync.com. You can change it at any time using Cookie settings.