Menu

Users, roles and permissions

Who is in the organisation, what each role carries, and why none of them grants engineering authority.

Demonstration project - no figure here describes a real facilityChanges are not saved
Why

Membership is read from the project's own records. An invitation needs Clerk, which is not configured.

Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.

People

10

Administrators

1

With engineering authority

1

With no project access

1

An organisation role grants no engineering authority

An owner can invite people, change settings and read the audit trail. They cannot approve a hydrotest procedure, and granting it to themselves would put a signature next to somebody who never read the document.

People

Organisation members
PersonEmailOrganisation roleDisciplineProject capabilitiesMay approve
A. Rahmana.rahman@zemerc.examplememberPIPauthor, viewerNo
N. Okonkwon.okonkwo@zemerc.examplememberPIPchecker, viewerNo
S. Lindqvists.lindqvist@zemerc.examplememberPROreviewer, viewerNo
R. Haddadr.haddad@zemerc.examplememberPROapprover, issuer, viewerYes
M. Silvam.silva@zemerc.examplememberINSauthor, checker, viewerNo
T. Adeyemit.adeyemi@zemerc.examplememberELEauthor, viewerNo
J. Novakj.novak@zemerc.examplememberCOMauthor, viewerNo
K. Mensahk.mensah@zemerc.exampleownernot an engineering roleproject_admin, viewerNo
D. Faroukd.farouk@reference-gas.examplememberPROreviewer, viewerNo
ZEMERC Supportsupport@zemerc.examplesupportnot an engineering rolenoneNo

Organisation roles

What each organisation role carries
RoleWhat it permitsAdministersEngineering authority
ownerAdminister the organisation, including billing and membershipYesNone
adminAdminister the organisation; cannot change billingYesNone
memberBelong to the organisation; all project access is granted per projectNoNone
supportNothing at all, unless an unexpired support grant existsNoNone

Invite somebody

Organisation membership only. Project access is granted per project.

Where project access is granted

On each project’s team page, one capability at a time. Granting approver or issuer asks for a reason, because “who decided this person may approve a hydrotest procedure?” is a question an audit asks and a membership table cannot answer.

Authentication is not configured

Clerk is the approved identity provider and no instance exists. Nothing has authenticated, no invitation can be sent, and the people listed here are the reference project’s own records.