Back to blog
For years, ReportPortal has used four project roles to control what users can see and do: Project Manager, Member, Operator, and Customer.
Our usage data shows that around 80% of users are assigned the Project Manager role. This indicates that the current roles do not always match how teams manage access.
ReportPortal 26.1 introduces a simpler structure. Instance administration, organization management, and project access will be managed separately.
Before you upgrade: Existing roles will be migrated automatically, but the migration can increase or reduce a user's project access. Administrators should review the changes below and check user access after the upgrade.
What Changes in ReportPortal 26.1?
Access will be managed at three levels:
Instance → Organization → Project
Instance-Level Account Types
ReportPortal will continue to use two account types:
Administrator — manages instance-level settings and user accounts.
Regular user — receives access through organization roles and project permissions.
Organization-Level Roles
At the organization level, there are two roles:
Manager — can perform all actions within assigned organizations.
Member — access depends on the permissions granted for individual projects.
An instance Administrator should assign the Manager role to users who need to manage the organization or access all its projects.
Note: Open-source ReportPortal instances include one organization by default. Support for multiple organizations is available as part of the premium Organizations functionality. Learn more in "Introducing Organizations: A new way to structure testing at scale."
Project-Level Permissions
At the project level, users can have one of two permission levels:
Editor — can perform all actions within assigned projects. Viewer — receives read only access within assigned projects.
Organization roles and project permissions are managed separately. For example, an organization Member can be an Editor in one project, a Viewer in another, and have no access to other projects.
What Happens to Existing Roles?
When moving to ReportPortal 26.1, existing roles will be mapped as follows:
Project Manager / Member / Customer → Member + Editor
Operator → Member + Viewer
Here, Member is the organization-level role, while Editor and Viewer define project-level access.
The Editor permission includes many capabilities previously available to Project Managers, such as managing project settings and members, working with test data, and performing other project-level actions.
The Manager organization role is assigned separately and provides full access within the assigned organization.
Previous role | Previous capabilities | Project permission in 26.1 | Capabilities in 26.1 |
|---|---|---|---|
Project Manager | Full project access: • Manage project settings • Manage project members • Report and manage all test results • Analyze and triage failures • Manage dashboards, widgets, and filters • View project members • Access Debug launches | Editor | Full project access: • Manage project settings • Manage project members • Report and manage all test results • Analyze and triage failures • Manage dashboards, widgets, and filters • View project members • Access Debug launches |
Member | Contributor access: • Report test results • Manage own test results • Analyze and triage failures • Manage dashboards, widgets, and filters when unlocked • View project members • Access Debug launches | Editor | Full project access: • Manage project settings • Manage project members • Report and manage test results • Analyze and triage failures • Manage dashboards, widgets, and filters • Perform all other project actions |
Customer | Limited contributor access: • Report test results • Manage own test results • Analyze and triage failures • Manage dashboards, widgets, and filters when unlocked | Editor | Full project access: • Manage project settings • Manage project members • Report and manage test results • Analyze and triage failures • Manage dashboards, widgets, and filters • Perform all other project actions |
Operator | Analysis-focused access: • View and analyze test results • Analyze and triage failures • Manage dashboards, widgets, and filters when unlocked • View project members • Access Debug launches | Viewer | Read-only access: • View project data • Search project data • Filter project data • No changes allowed |
What Should Administrators Do?
Before upgrading to ReportPortal 26.1:
Identify existing Members and Customers who should not receive Editor access.
Identify Operators who must continue triaging failures or managing dashboards, widgets, and filters. These users will need Editor permission.
Decide who should receive the organization Manager role.
After the upgrade, review organization roles and project permissions and adjust them where necessary.
Share Your Feedback
We want to understand how your team manages access today and what roles or permissions you may need in the future.
The survey takes approximately 2–3 minutes to complete.
Your feedback will help us plan future improvements to roles and permissions in ReportPortal.