You can view users under the Users tab of Organization Settings. To invite new users, click Invite New User on the right side of the page above the user list search bar.
Fill out user details and then click Save. Keep in mind, when adding the user's email, this is case sensitive and is used as the log in username, so be mindful to not capitalize this field.
This will send the new user an invite via email. Remind new users to check their spam folder if they can't find the invite!
User Permissions
To give an invited user permission (or edit permissions for an existing user) click + Add a Team to add a new team.
A list of choices based on existing teams will then be available to choose from. Once a team is chosen, you can give the user "Manager" or "Can Edit" permissions by checking the corresponding boxes.
In this example, a user is being added to the sales team as a rep (non-manager) - they will be able to create and view their own jobs. To give more granular permission, use teams that limit the number of phases to a smaller set. Sales covers all phases from address to proposal. You can also click "Remove" to remove a person from a particular team.
Note: if a user has accepted the invite to join Sighten but has not yet been assigned to a team, they will be unable to load any phases of their organization’s projects. Furthermore, the pipeline page will appear blank. In order to remedy this, an Organization Admin with Manager permissions to the settings phase must assign the user to at least one team with specified permissions in order to grant access.
Can I edit User Settings so a user only has access to his/her own jobs?
Yes, you can do this! For any team, a user will only have access to other jobs if the "Manager" checkbox is checked. If you'd like to ensure a user only has access to his/her own jobs, make sure that the Manager checkbox is turned off, and only the Can Edit checkbox is checked.
To do this, you may follow these steps:
- Go to https://engine.sighten.io/gen/#/settings/organization
- Under the Users tab, choose the user that you'd like to edit or check permissions for (this also applies for when you're trying to add a user).
- If it's an existing user, click Edit (you'll find this on the upper right side of the screen). If inviting a new user, make sure the Settings under Teams is as specified below.
- Under Teams, ensure that Manager checkbox is left blank and the Can Edit? checkbox is checked (highlighted on the screenshot below).
- Click Save on the upper right side of the screen.
Here's a screenshot for reference:
Teams
Teams are a collection of functions (or phases) that a given team should have access to. The "Manager" and "Can Write" permissions are granted at the user level - teams specify the phases that can be accessed.
For example, the sales team has access to view all phases - from address to proposal. The address team only has access to address. A new team could be created, maybe a canvasing team, that has access to address and contact. When you add users to teams, they are only given permissions to the phases enabled within the team (shown in blue below). However, if someone is a member of multiple teams, their visibility will include any phase that is enabled on any of their teams.
Admins can use the teams available out of the box, modify them, or create their own.
Determining Access
Once your team phases are set up, you can add your users to the teams and determine their level of access on two levels - Manager vs. Rep and Read Vs. Write.
Manager vs. Rep permissions:
a user that does not have manager selected will only have access to jobs that they created or that have a phase directly assigned to them
a user that does have manager selected will have access to all jobs included in the above bullet and all jobs that are owned by their organization and a phase that they manage is open.
- Note: that manager permissions take precedence over rep, so if someone is a member of two teams and has manager access to a phase in one and non-manager in another, the user will be able to manage that phase.
Read vs. Write permissions:
a read user is able to see all of the data that they have permission to but cannot make any updates/changes
- a write user has all of the above bullet and is able to make changes
Note: that write permissions take precedence over read, so if someone is a member of two teams and has edit access to a phase in one and not in another, the user will be able to edit that phase.
Related Articles
You might also want to check out these related articles: