Types of view rights

Tags: Flow


A view right is the level of data visibility that is granted to a user. There are two levels of view rights, first you can control what teams users see, then you can control what level of data for teams users see.

Team metrics view rights

The team level view rights will dictate which teams a user can see by default. Here are the options:

  • 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. This information can be seen on the User's details page.
  • No Team: The user will only see their own metrics
"Inherit" means the view rights will be inherited from the permission levels above it.

Contributor metrics view rights

The contributor level view rights will dictate whether or not a user can see individual contributor metrics in addition to their own. Here are the options:

Can users see individual contributors’ metrics?

  • Yes: The user will be able to see individual contributors’ metrics 
  • No: The user will not be able to see individual contributors' metrics, only aggregated team data.

Tip: "Inherit" means the setting will be inherited from the permission levels above it.

Common view right templates

Every company has different use cases, responsibilities, and needs for what data they want to grant users access to. View rights are structured in a way 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.

Setting: "All Teams" / "Individual 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.

Setting: "All Teams" / "Individual 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.

Setting: "Only Their Own Team" / "Individual Metrics: Yes"

Tip: Users with this configuration will be able to 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, Joe’s role as a reviewer will appear in the review and collaborate 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 understand their numbers relative to their team’s aggregate trends - without the ability to see their teammates specific contributions.

Setting: "Only Their Own Team" / "Individual Metrics: No"

No Teams 

Use case: Team member who won't see anything but their own data. For the individual user that wants to use their data for personal feedback and growth.

Setting: "No Teams" / "Individual Metrics: No"

Tip: When "No teams" is selected the option to view individual contributor metrics will be grayed out and will default to "yes" but the user will only be able to see their own data as depicted in the image.

back to top

If you need help, please email support@pluralsight.com for 24/7 assistance.