> ## Documentation Index
> Fetch the complete documentation index at: https://docs.isometric.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account roles

> The four roles you can assign to a member of your Isometric organization, what each role can do across Certify and the Registry, and how to give a Custom access user access to individual projects

Each member of your organization has a role. The role is set when the user account is created, and can be edited at any time. See [User management](/user-guides/user-management).

## Roles

Users may be assigned one of four main roles:

| Role              | What the role covers                                                        |
| ----------------- | --------------------------------------------------------------------------- |
| **Admin**         | Can view and edit all projects, and edit settings                           |
| **Editor**        | Can view and edit all projects                                              |
| **Viewer**        | Can only view all projects (Verifier organizations: can also manage issues) |
| **Custom access** | Can only view or edit explicitly assigned projects                          |

A user who does not belong to an organization shows as **Individual**.

## Permissions

### Admin

Only an Admin may:

* Add, edit and remove users, and change the role of another user.
* Assign project access to a Custom access user.
* Deliver, retire and transfer credits on the [Registry](/user-guides/registry/deliver-credits).
* Create custom credit accounts and add beneficiaries.
* Submit orders and create order delivery schedules.
* Manage issuance forecasts.
* Create and invalidate API access tokens and client secrets.
* Change the setting that lets new users with your email domain join the organization automatically.

### Editor

An Editor can create and change project data in Certify for every project in the organization. This covers the [PDD](/user-guides/certify/project-design), the [LCA](/user-guides/certify/lca), the [GHG statement](/user-guides/certify/ghg-statement) and the datapoints behind them.

An Editor cannot manage the team, and cannot perform any Registry action in the Admin list above.

### Viewer

A Viewer can read every project in the organization, but cannot change project data.

For Verifier organizations, a Viewer can also raise and manage issues in the [log of issues](/user-guides/certify/log-of-issues). This includes editing, publishing and deleting an issue, and setting the supplier's responsible user.

### Custom access

A user with custom access sees only the projects they are assigned to. Use this role for a contractor, a consultant, or an employee who should not see your whole portfolio by default. See [Project-level access](#project-level-access) below.

## Project-level access

Alongside the organization role, each user holds a role on each individual project.

For an Admin, an Editor or a Viewer, the project role follows automatically from the organization role. The user is added to every project in the organization, including any project created later. You do not need to assign anything.

A user with custom access is not added to any project by default. Access is granted on a per-project basis.

<Steps>
  <Step title="Edit the user">
    On the [User management page](https://registry.isometric.com/account/settings/users), click on the user's row to open the Edit dialog.
  </Step>

  <Step title="Set the role to Custom access">
    In the Edit dialog, change the **Role** dropdown to **Custom access**. The **Project access** table appears below. It lists the projects in your organization.
  </Step>

  <Step title="Choose a role for each project">
    Select **Editor** or **Viewer** against a project. A verifier organization selects **Verifier** instead — this gives the user read access to submitted project data and lets them raise and manage issues in the [log of issues](/user-guides/certify/log-of-issues). Leave a project as **No access** to keep it hidden from the user.
  </Step>

  <Step title="Save">
    Click **Save**. You can return and change any project role later.
  </Step>
</Steps>

## Summary

* Give **Admin** to the people who manage the team, hold the API credentials, and deliver credits.
* Give **Editor** to the people who write and submit project documentation.
* Give **Viewer** to the people who need to follow progress but should not change data.
* Give **Custom access** to anyone who should see one project rather than your whole portfolio.

If you are not sure which role a person needs, start with the narrower role. An Admin can widen it at any time.


## Related topics

- [User management](/user-guides/user-management.md)
- [Create issuance forecast](/user-guides/registry/create-issuance-forecast.md)
- [Log of Issues](/user-guides/certify/log-of-issues.md)