Understand Opries permission levels

A system permission controls what a person can do in Opries for a particular organisation. It is assigned through User access when an invitation is prepared or an existing person's access is edited.

Use the lowest permission level that allows the person to do their work. A permission can be changed later without deleting the Person record or their organisational history.

Reader

A Reader can read approved organisation information that is available to them and use ordinary reader experiences such as assigned learning.

Reader access does not allow the person to change drafts, approve governed records or administer the organisation.

Editor

An Editor has reader access and can create or change drafts, then submit those changes for review.

Editing does not approve or publish a change. The governed review and publication steps remain separate.

Approver

An Approver has reader access and can review governed changes and approve or reject them according to the applicable workflow.

Approval does not automatically make information public, create a delegation or authorise an external action. Publication and organisational authority remain separate decisions.

Organisation administrator

An Organisation administrator manages people, organisation access and Opries platform settings for their organisation. This includes assigning organisation permission levels through User access.

This permission should be limited to people who genuinely need to administer the organisation's Opries environment. It does not, by itself, make the person an office holder, committee member, manager or authorised delegate.

Platform administrator

Platform administrator is an internal Opries-wide permission used to operate the platform across organisations. It is managed by Opries and is not an organisation-managed role.

Platform access must still respect tenant isolation, auditability and the purpose for which access is required.

Permissions are not organisational authority

System permissions are deliberately separate from:

• participation roles, such as volunteer, staff or management committee;
• restricted-content access groups, which provide access only to explicitly assigned restricted information;
• governed role descriptions, which define responsibilities, authority and limitations; and
• approved appointments and delegations, which establish effective organisational authority.

Changing a person's system permission does not appoint them to a governed role, give them delegated authority, approve a document or make information public.

Assign or change a permission

1. Open the account menu for the active organisation.
2. Select User access.
3. Add the Person first if they do not already have a Person record.
4. Prepare their invitation or open the action menu beside an existing user.
5. Select the required System permission.
6. Review the change before saving or sending the invitation.

Permission changes should record who made the change, the previous and new levels, and when it occurred. Disabling or archiving access should preserve the Person record and its history while removing effective application access.