Faros has four roles available to all your users: Owner, Administrator, Analyst and User.

Professional Edition organization have two user roles available for their users: Owner and Analyst, while Enterprise Edition organizations have all four roles available.

Summary of user roles

User role permission details

Assigning roles to users

Owners are the only people who can change the roles of other users within Faros. To update someone’s role:

• Go to Settings → Users
• When creating a new user, you will have the option to assign them to any of the roles.
• For existing users, select edit option in the “⋮” menu on the user’s row. There will be a popup where you can edit the role.
• For customers creating users through an SSO integration, the last page of the SSO setup allows you to configure default user roles or map groups to specific roles. If you are creating users this way make sure to always include the base 'user' role in addition to more specific ones.

Defining user-specific data

Administrators and analysts have access to all the data that is tracked and measured in Faros, while a user will only be able to see data and reports relevant to themselves or, if they are a team lead, all members in their team and child teams. This is true, whether the user is looking at dashboards or querying the reporting database directly via questions.

Example

Assume our sample org has the following team structure:

The chart below is from the Engineering Productivity module and shows the ratio of unplanned to total work for Team A and its subteams (Team A1 and Team A2) .

Tasks are associated with a team via the board (or project). Because of the filter on Team A, This chart will use tasks that belong to boards owned by Team A, Team A1, and Team A2. Note that tasks are also assigned to individual employees.

If the person viewing the report is an admin or analyst, the report will use all the tasks in those boards to calculate the ratio, regardless of whom they are assigned to.

If the user viewing the report is not an analyst or admin, the report will only use tasks that are associated with themselves. If the user is a team lead, the report will also use tasks associated with members of their teams and sub-teams.

Here is a subsample of the task data across all teams:

When an administrator views the chart, the ratio will be calculated from rows 1-4, as they are all the tasks for boards associated with TeamA and its sub-teams (as that was the filter on the original chart.) If they wanted to view all the tasks listed above or see the ratio for all teams, they would need to set the filter to “all-teams”

The team lead for Team A will see a ratio calculated from rows 1-3, those are the rows with the tasks in Team A and the employee assignees or creators are in Team A’s reporting structure.

Employee A1 will only see the ratio calculated from rows 1 & 2. Row 6 is not included, as the work is not in a Team A board. (Note that if Employee A1 wanted to view all their work across all boards, they would use the “all-teams” filter instead of the “Team A” filter, and then the ratio would use rows 1, 2, and 6.)

The team lead for Team B only uses row 4 to calculate the ratio.

What objects are scoped to employees?

Records that are not in the above tables (such as steps in a flow) are not scoped to individual people, so all users will be able to see them in their dashboards and reports.