Understanding Intuety platform user roles
A guide to the four Intuety user roles, Author, Reviewer, Project Admin and Company Admin, including what each role can do, who typically holds it, and the training in place. Also covers caveats on supply chain access, the document creation module, and how live training sessions are agreed with customers.
This document explains the user roles available in the Intuety platform. It covers what each role can do, who in your organisation typically holds it, and the training we have in place to support people in that role.
A user can hold any combination of these roles. Roles are additive, so assigning more than one simply adds those permissions to the same account. There is no need to create separate logins for people who wear more than one hat.
Important caveats- Supply chain management is only available to paying organisations. It is not accessible on trial or non-paying accounts, regardless of the roles a user holds.
- Document creation (the Author ability to create new RAMS in the platform) is an additional module. Uploading existing RAMS is available as standard; creating new RAMS through the guided authoring workflow requires the module to be enabled on your organisation.
- Live delivered training sessions are not offered by default. They are agreed with customers on a case-by-case basis where the scenario warrants it, and are not something available on request as standard.
|
Role |
Who typically holds it |
What they can do |
Training in place |
|
Author |
People who write and produce risk assessments and method statements. Typically site or project engineers, SHEQ advisors, supervisors and any operational staff responsible for producing RAMS. |
|
|
|
Reviewer |
Internal reviewers, approvers, SHEQ leads and anyone responsible for signing off RAMS produced by internal teams or contractors. |
|
|
|
Project Admin |
Project managers, contract managers, PMO or operations coordinators responsible for the setup and lifecycle of projects and sites. |
|
|
|
Company Admin |
Platform owners within the organisation, typically SHEQ directors, IT/system owners or heads of operations who look after configuration and user access. |
|
|
Combining roles
Because roles are additive, most people in your organisation will hold more than one. A few examples of how they typically stack:
|
Example person |
Typical role combination |
|
A subcontractor RAMS author |
Author only. Produces RAMS for review by their client. |
|
A SHEQ advisor for a contractor |
Author and Reviewer. Writes their own RAMS and reviews and approves colleagues. |
|
A project manager who also reviews |
Reviewer and Project Admin. Sets up projects and approves RAMS attached to them. |
|
A platform owner running the account |
Company Admin plus any of the above, depending on how hands-on they are. |
|
A site engineer producing RAMS |
Author only. |
Author and Reviewer: supported by in-app tooltips and full guided interactive walkthroughs. Live delivered training may be included where agreed with the customer, but is not offered by default.
Project Admin and Company Admin: supported by knowledge base articles, written guides, and interactive in-product guides.