Roles
Users may be assigned one of four main roles:
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.
- 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, the LCA, the 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. 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 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.1
Edit the user
On the User management page, click on the user’s row to open the Edit dialog.
2
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.
3
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. Leave a project as No access to keep it hidden from the user.
4
Save
Click Save. You can return and change any project role later.
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.