Skip to content
Need Help?
  • There are no suggestions because the search field is empty.

How do Permissions work?

Each User in the system is assigned two roles; an Account Role and a Project Role. Both Roles work together to determine what actions the User can take within the Platform.

Account Roles

The Account Role primarily determines if the Role requires a paid license. The table below outlines the different Account Roles available.

Account Role Ability License Type
Account Administrator Complete control over the account (users, templates, settings, etc.) and are automatically set as Project Administrators on all Projects.  All Account Administrators are equal in permission. Paid
Account User Account Users are associated and paid by the account and have access to projects as defined by their Project Role. Account Users have no access at the Account Settings area. They may have access to Project Settings based on their Project Role. Paid
Account Reviewer Account Reviewers can be Project Reviewers or Project Read Only Users. This is a free license only available within the Pro package. Free
Account Read Only Account Read Only can only be  Project Read Only Users. This is a free license available within the Standard and Pro packages. Free

 

Project Roles

Each User is assigned a Default Project Role in the system - this is the role the User inherits when they are initially added to a project. Their Project Role can subsequently be changed and Users can have different roles on different projects. 
Project Roles are available based on the Users Account Role as outlined in the table below.
Project Role Ability Account Role Needed
Project Administrator Complete control over a Project (Users, Settings, Lists, Entries, etc.). All Account Administrators are required to be Project Administrators. Account Administrator or Account User
Project Manager Complete control over a Project (Users, Settings, Lists, Entries, etc.). Account User
Project User Can View, Add, Edit, Archive and Delete Document Entries based on the specific Document Templates permission structure. This role has no access to Project Settings. Account User
Project Designer Can View, Add, Edit, Archive and Delete Document Entries based on the specific Document Templates permission structure. This role has no access to Project Settings. Account User
Contractor Can View, Add, Edit, Archive and Delete Document Entries based on the specific Document Templates permission structure. This role has no access to Project Settings or the File Cabinet. Account User
Project Reviewer Users with this Role can only add Comments and edit the Workflow on allowed Document Templates. Account User or Account Reviewer
Project Owner Users with this Role can only read Entries in allowed Document Templates. Account User, Account Reviewer or Account Read Only
Read Only Users with this Role can only read Entries in allowed Document Templates. Account User, Account Reviewer or Account Read Only

NOTE: New roles cannot be added, and existing role labels cannot be modified

 

Tip: Understanding Project Roles

Some Project Roles in FACS currently share the same permissions but are provided as separate role options to help organizations better organize and manage project participants.

Project User and Project Designer have the same default permissions. These separate roles allow organizations to distinguish field personnel from design personnel and support permission differences if needed.

Project Owner and Read Only have the same default permissions. These separate roles allow organizations to distinguish project owners from other view-only participants, such as program managers, consultants, or executive reviewers.

Providing separate role labels with matching permissions gives organizations greater flexibility when managing users, reporting on project participation, and configuring future access requirements.

 

 

If you have any questions, or need additional assistance, please reach out to our support team at support@facsware.com and we will be happy to assist you.