# General Translation Platform: Roles & Permissions URL: https://generaltranslation.com/en-GB/docs/platform/orgs/roles.mdx --- title: Roles & Permissions description: Understand the default roles and permissions available in your organisation --- Every member of an organisation is assigned a **role** that determines what they can access and change. Roles are assigned when a member is invited, but can be changed later by an Owner or Admin. ## Organisation roles When an organisation is created, five default roles are set up automatically: | Role | Description | | ------------- | --------------------------------------------------------------------------------------------------------------------- | | **Owner** | Full access to everything. Can delete the organisation and transfer ownership. Bypasses all permission checks. | | **Admin** | Full access to all organisation and project settings, members, billing, and translations. | | **Developer** | Technical access to projects—API keys, GitHub integration, Locadex, and usage data. Cannot manage members or billing. | | **Editor** | Can read, edit, and review translations. No access to settings, members, or billing. | | **Member** | Can view the organisation but has no specific permissions. Useful as a base role with additional per-user overrides. | ## Enterprise roles Enterprise accounts have an additional layer of roles for managing multiple organisations. For details on enterprise roles and permissions, [contact us](https://generaltranslation.com/contact). ## Permissions reference Permissions are grouped into categories. The table below shows which default roles have access to each permission. ### Organisation permissions | Permission | Owner | Admin | Developer | Editor | Member | | -------------------------- | :---: | :---: | :-------: | :----: | :----: | | Update org settings | ✓ | ✓ | | | | | Manage projects & plan | ✓ | ✓ | | | | | Manage members | ✓ | ✓ | | | | | View usage | ✓ | ✓ | ✓ | | | | Read GitHub integration | ✓ | ✓ | ✓ | | | | Write GitHub integration | ✓ | ✓ | ✓ | | | ### Project permissions | Permission | Owner | Admin | Developer | Editor | Member | | ---------------------------- | :---: | :---: | :-------: | :----: | :----: | | Update project settings | ✓ | ✓ | | | | | Read API keys | ✓ | ✓ | ✓ | | | | Create & delete API keys | ✓ | ✓ | ✓ | | | | Read project context | ✓ | ✓ | | | | | Write project context | ✓ | ✓ | | | | | Read Locadex settings | ✓ | ✓ | ✓ | | | | Write Locadex settings | ✓ | ✓ | ✓ | | | ### Translation permissions | Permission | Owner | Admin | Developer | Editor | Member | | --------------------------------- | :---: | :---: | :-------: | :----: | :----: | | Read translations | ✓ | ✓ | | ✓ | | | Edit translations | ✓ | ✓ | | ✓ | | | Review & approve translations | ✓ | ✓ | | ✓ | | ### Roles & billing permissions | Permission | Owner | Admin | Developer | Editor | Member | | ------------------------- | :---: | :---: | :-------: | :----: | :----: | | View roles | ✓ | ✓ | | | | | Create & delete roles | ✓ | ✓ | | | | | Assign roles to members | ✓ | ✓ | | | | | View billing | ✓ | ✓ | | | | | Update billing | ✓ | ✓ | | | | ## Permission inheritance Permissions cascade down the hierarchy: **Enterprise → organisation → Project** If a user has a permission at the enterprise level, they automatically have it for all organisations and projects within that enterprise. Similarly, organisation-level permissions apply to all projects in that organisation.