Permissions

Permission Overview

There are a lot of complications and nuance to permissions but in general there are two things being controlled by any type of permission: how much access should this user have and what kind of access is it?

Permissions can be combined in a myriad of different ways for very granular control. At the end of this article will be a series of examples displaying this. 

Levels of Access

Organisation - The overall group of data for a signage owner. A company using SignAgent to making signs will have many organisations because they have many clients. A company managing 

Project - The scope of work. An organisation can have multiple projects occurring simultaneously. Planning for a new building, a rebrand, or basic maintenance could all be projects occurring at the same time. There are different kinds of projects depending on whether signs are being designed, built, or managed long-term. 

State - A step of a project. A project should have multiple states to outline the process a sign will pass through. The step of Sign Review and Sign Installation are common examples where users would be given permissions to a state.

Organisation Level Access

Receiving organisation level permissions will give access to all signs within an organisation. If that access also grants editing capabilities, the user can edit any project, sign, location plan, or underlying setting. 

Inviting Users to an Organisation Article

Organisation Owner - The owner of  the data being stored in SignAgent. The person who owns the signs owns the data. An owner does not require a paid license in order to be given access. Designers and fabricators should include their clients as an owner.

Admin - This user has full access to all aspects and signs within an organization. They must have a paid license.

Viewer - This user can see all signs in the organization. They cannot make changes, but can leave comments. They may be invited in without having a paid license.

Project Level Access

Project level access will allow users to see signs associated with only that project. They will not see that other projects exist and cannot see signs that exist outside of the project. There are three types of projects: Design, Build, and Manage. Each is used depending on the type of work being done. For more information on the three project types and their associated types of licensing, see this article.

Inviting Users to a Design Project Article

Inviting Users to a Build Project

Editor -  This user has full access to edit all signs in this project, and can change some other settings in the organization. Anything outside of the project will be hidden and inaccessible. They must have a paid license of SignAgent. A Member cannot edit location plans or sign types since that would change signs they do not have access to. The terminology for a editing of each project type is:
     Design Project- Manager
     Build Project- Installer
     Manage Project - Manager

Viewer - This user can see all signs in the project. They can't make changes but can leave comments on signs. Anything outside of the project will be hidden and inaccessible. They may be invited in without having a paid license.

State Level Access

State level access is somewhat different than organisation or project level access in that it confers the ability to approve signage for a specific step in a project. This is an add on permission that can be given to users with other levels of access or none at all. An admin added to a state will be able to approve signs in that one state while still editing all signs. A user added to a state with no other access will only have approval permissions for the signs in that state. 

Inviting Reviewers to a State

Design Project  - Reviewer
Build Project - Assigned

 

Examples

All the following examples would take place in a single organisation

1. User has viewer access to the organisation, member access to a Design project called "Renovation", and reviewer access to the "Internal Review" state within that project. 

• They can see every sign, all projects, and all locations. 
• They can edit the "Renovation" project and any signs it contains
• They can approve signs within the "Internal Review" state

2. User has installer access to a Build project 1 and is a reviewer of the "Approval" state in a separate Design project 2. There are 3 other projects they are unconnected to. 

• Access to a Build project gives them access to the build interface (kanban board)
• Access to the Design project gives them access to the design interface (left-hand sidebar and map)
• They can see all signs in Build project 1 and Approval state using the design interface 
• They can see and edit all signs in Build project 1 using either the Design interface or the Build interface
• They can approve all signs in the Approval state using the Design interface