Visibility
Control role-based visibility and data access for metrics, search results, and the deploy risk indicator across your organization.
Overview
The Visibility settings page controls who can see what within your Koalr organization. It covers three areas: the overall metrics visibility mode, data visibility toggles for individual developer metrics, and the deploy risk topbar indicator per-role settings.
Navigate to Settings > Visibility to configure access controls. Only Admins and Owners can modify these settings.
Metrics visibility mode
Choose one of two modes that govern how metrics are exposed across your organization.
Full Transparency
The default mode. All organization members and viewers can see all metrics for all team members, including per-developer PR stats, cycle time, and review metrics.
This mode is recommended for teams that value open culture and shared ownership. DORA research indicates that teams with high transparency ship more frequently and have lower change failure rates.
Role-Based Access
Restricts individual developer metrics based on the user's role. When this mode is selected, a permissions matrix appears where you can customize access for each feature area.
Default behavior in Role-Based mode:
- Owner and Admin -- always have full access to all features and data
- Member -- sees their own individual metrics plus team aggregates
- Viewer -- sees only team-level aggregates and DORA metrics
Permissions matrix
When Role-Based Access is selected, a table appears listing each feature area (DORA Metrics, Team Aggregates, Individual Developer Metrics, Code Review Bottlenecks, Flow and Focus Metrics, Surveys and SPACE Scores, AI Analytics, Coverage and Quality, Reports, Search, Settings and Integrations). For each feature, you can set the Member and Viewer access level to one of:
| Level | Meaning |
|---|---|
| Full | Complete access to all data in this area |
| Own only | Can see only their own data (individual metrics only) |
| None | No access to this feature |
Owner and Admin columns are fixed at Full and cannot be changed. The Settings and Integrations row is always restricted to Admins and Owners regardless of mode.
Search visibility
The global search (accessed via the command palette) respects the selected visibility mode:
- Full Transparency -- search returns all developers, pull requests, issues, repositories, reports, and teams to every user.
- Role-Based Access -- search results are scoped to entities the user is permitted to view. Members can only find their own developer record; Admins see everything.
Data visibility
Individual Developer Metrics Visibility
A toggle that controls whether all authenticated users can see individual developer metrics (PR velocity per person, coverage by developer, review profiles). When disabled, only Admins and Managers can access individual-level data.
This setting is independent of the metrics visibility mode above and provides an additional layer of control. It is particularly relevant for GDPR compliance, as disabling individual visibility reduces the exposure of personally identifiable performance data.
Changes take effect immediately for all users.
Deploy Risk topbar indicator
The deploy risk indicator is a live count of high-risk and critical PRs shown in the top navigation bar. This section controls which roles see the indicator.
| Role | Default | Configurable |
|---|---|---|
| Owner | Always visible | No |
| Admin | Always visible | No |
| Executive | Visible | Yes |
| Manager | Visible | Yes |
| Member | Visible | Yes |
| Viewer | Never visible | No |
Toggle each configurable role on or off and click Save changes to apply.
Roles overview
Koalr has six roles, assigned per user on the Members settings page:
- Owner -- full access, can transfer ownership
- Admin -- full access to all features and settings; can assign any role below Admin
- Executive -- read access to all team-level and org-level metrics; no individual developer data unless the org-level visibility toggle is on
- Manager -- individual developer metrics scoped to the team(s) they lead; Managers see per-developer data only for their direct reports, not the full org
- Member -- standard access, scoped by visibility mode; sees own individual metrics plus team aggregates
- Viewer -- read-only access; sees team-level aggregates and DORA metrics only
Manager team scoping
When a Manager accesses individual developer metrics (per-developer PR stats, review depth, coverage breakdowns), Koalr automatically filters results to the members of the teams they lead. This scoping happens at the API level — Managers cannot access individual data for engineers outside their teams even via direct API calls.
Team leads are designated in Settings → Teams by assigning a member the Lead role within a team. A user must be a Lead in at least one team for the Manager scoping to take effect.
Hierarchical role assignment
Roles can only be assigned by users with a strictly higher rank. The hierarchy from highest to lowest is:
Owner → Admin → Executive → Manager → Member → Viewer
An Admin can assign Executive, Manager, Member, or Viewer. An Admin cannot assign another Admin (only an Owner can do that). This prevents privilege escalation through role reassignment.
Role-based visibility only takes effect when the visibility mode is set to Role-Based Access.