A view right is the level of data visibility granted to a user. View rights control which teams users see and the level of data for those teams.
Team metrics view rights
The team level view rights dictate which teams a user can see by default. This is referred to as scope. The team level view rights are:
- All teams: The user can see every team
- Their own teams: The user can see only the teams that they've been added to and any teams nested under those teams.
- No Team: The user can only see their own metrics.
Tip: Inherit means the setting is inherited from the permission levels above it.
Contributor metrics view rights
The contributor level view rights dictate whether a user can see other users' individual contributor metrics. This is referred to as depth.
Can users see individual contributors’ metrics?
- Yes: The user can see individual contributors’ metrics.
- No: The user cannot see individual contributors' metrics, but can see aggregated team data.
If the view rights scope is set to No teams, then the depth is automatically set to Yes. This means the user can only see their own metrics. You cannot change this. No matter what the depth is set to, users can always see details about their own metrics in reports.
Common view right templates
Every company has different use cases, responsibilities, and needs for what data users should access. View rights are structured to accommodate any use case you may have. If you aren’t sure where to start, here are some standard use cases and recommendations.
All teams and individual contributor visibility
Use case: Flow Administrators (Global rights). These users can see the entire organization’s data, as well as individual contributors' data. These superusers need to see the organization’s data in full.
Which teams can users see by default? All Teams
Can users see individual contributors' metrics? Yes
All Teams and no individual contributor visibility
Use case: Executives. These users often use data to run high-level analysis for their teams and the department. Seeing individual contributors’ data is too specific.
Which teams can users see by default? All Teams
Can users see individual contributors' metrics? No
Only their own teams and individual contributors’ metrics
Use case: Managers or team leads. These users learn from data to provide feedback and coaching to help their teams grow. This permission set allows a manager to see their own team members’ metrics without the permission to review other teams’ data.
Which teams can users see by default? Their own teams
Can users see individual contributors' metrics? Yes
Tip: Users with this configuration see limited information about users who are not on their team, but who collaborated with team members. For example, if Joe is not on the the Alpha team, but he did a lot of code review for the Alpha team, then Joe’s role as a reviewer appears in the reports for the Alpha team.
Only their own teams and no individual contributors’ metrics
Use case: Team member plus an overview of their team. This is the most common user view right. Individual users use their data for personal feedback and to understand their numbers relative to their team’s aggregate trends - without the ability to see their teammates' specific contributions.
Which teams can users see by default? Their own teams
Can users see individual contributors' metrics? No
No Teams
Use case: Team member who won't see anything but their own data. This is for the individual user who wants to use their data for personal feedback and growth.
Which teams can users see by default? No teams
If you need help, please contact Pluralsight Support.