Product

Introducing Organizations: A new way to structure testing at scale

Back to blog
userReportPortal Team
calendarJuly 17, 2026

At ReportPortal, our goal has always been to make life easier for testing teams. In our next major release, we're introducing Organizations, a feature built for enterprise users who run many projects, streams, and departments at once. It changes how you structure, manage, and analyze test data when a single project is no longer enough.

What are Organizations?

Organizations are a two-level hierarchy for structuring data across projects. Instead of handling everything inside a single project, you manage it at the organization level, with your projects grouped underneath. For larger teams, that means a more flexible and scalable way to keep test data organized.

ReportPortal runs in a lot of highly regulated environments and complex enterprise setups, where testing spans many teams, products, and compliance boundaries. Until now, it worked with a single, flat project-level hierarchy. That structure is fine for smaller setups, but it doesn't map well onto a large organization. Once you need to separate tests across teams, products, or development streams, a flat list of projects gets in the way, and Organizations give you a structure that matches how bigger teams actually work.

What you get with Organizations: 

  • keeps each team's test data isolated, which matters in regulated and security-sensitive environments 

  • scales test reporting across many teams and products without outgrowing a flat project structure 

  • gives central oversight of projects while each team works independently, and applies shared settings across many projects at once  

Example: Take a bank that runs its testing in ReportPortal. Payments, lending, and customer accounts each belong to a different team, and their test data shouldn't be visible across streams: logs and attachments can carry sensitive records, so access is kept on a need-to-know basis. With Organizations, each team gets an isolated space inside the same department or instance, while a QA lead can still look across teams for the bigger picture.

How it works

Inside an Organization, you split tests across projects in whatever way fits your work. You can also set general settings, such as how long launches, logs, and attachments are kept, across several projects at once instead of one by one. If a project needs different settings, you can still set those separately.

Roles and permissions

We have simplified the role model by introducing a clear two-level permission structure based on Organizations and Projects.

At the Organization level, there are two roles: 

  • Manager – has full access to the organization, can manage all organization settings, and has access to every project within the organization.

  • Member – cannot modify organization settings or manage the organization itself. Members only have access to the projects they are assigned to. 

For Members, permissions are further defined at the Project level

  • Viewer – has read-only access to the assigned projects. 

  • Editor – can create, edit, and manage all content within the assigned projects.

What's next

This is the first release of Organizations, not the finished picture. Next, organization settings will grow to cover integrations, notifications, and defect type customization, so you can set these once at the organization level and have them apply across every project underneath. After that we're adding organization-level widgets and dashboards, so you can see data across all the projects in an organization in one place.

Organizations are also a necessary step toward portfolio-level dashboards. Once test data is structured at the organization level, we can roll it up into a portfolio view that spans several organizations. For leadership, that gives one read on testing health across the whole product portfolio, which makes it easier to see where quality risk is building up and to make release calls without digging through individual projects.

How to get Organizations

Organizations will be introduced in the next major ReportPortal release as part of our premium offering. You'll be able to find details about available plans and features on our pricing page after the release.

If you'd like an early look, have any questions, or are interested in seeing the upcoming capabilities in action, get in touch to book a demo. During the session, you'll learn more about the new features, discuss your use cases, and explore ReportPortal plans and pricing options.

For teams running several projects or juggling multiple squads, Organizations will take a lot of the manual work out of managing test data at scale. We'll keep building on it from here.

Be among the first to experience what’s next

The next major ReportPortal release is coming soon. ReportPortal is evolving from a test automation reporting solution into a unified QA Intelligence platform – bringing manual, automated, and agentic testing together in one place.

The upcoming release will introduce a new experience for managing testing activities across teams. In addition to Organizations, you'll also get access to powerful enterprise capabilities such as Test Management, along with many more enhancements.

Join the closed beta

Would you like to explore the new ReportPortal experience before the official release?

Complete the form to request access to our closed beta environment. Our team will contact selected participants and provide everything needed to start testing and share feedback.