If you're using productboard to manage multiple products, you can either manage all products out of a shared productboard project (environment), or across several productboard projects.

The best option for you will depend on how interrelated or discrete your products are.

Managing multiple products out of one project

For organizations with interrelated product offerings with overlapping user bases, standardized product prioritization processes across all products

Benefits of using just one productboard project:

  • Shared Insights board You'll have a common repository of product ideas, requests, and feedback from colleagues and customers including inputs on all products.
  • Shared prioritization criteria – Fields like objectives, segments, and drivers can span across all products' feature ideas.
  • Shared Roadmap – Visualize all products' features in a single portfolio view of your roadmap.

Additional functionality to help you manage multiple products and teams in one productboard project:

  • Multiple release groups – If you have multiple teams running on different release schedules you can manage these each as a separate release group in the same productboard project.
  • Customizable field sharing settings – Optionally, restrict access to certain data fields to just makers or make them private.
  • Capture saved views – Save views of your boards that show just the data most relevant to your product area. Optionally, customize the sharing settings of these views so they are kept private, only shared with certain roles, or select individuals. Views could also be saved that capture data spanning all products for a holistic view of what's being prioritized, planned, and delivered.
  • Tagging – You can pre-tag inputs arriving as notes on your Insights board, whether they're arriving by email, Slack, Zendesk, Intercom, or Chrome extension. These tags can then be used to help product managers find and process the incoming notes that matter most to them.
  • Multiple Jira integrations – Push features into multiple Jira projects or instances.
  • SAML SSO  – Manage everyone's access to productboard in one place.

Limitations of using just one project:

  • User roles and permissions are at the project level, so anyone invited into your project will have access to all products.
  • The Roadmap only displays one release group at a time. If you have multiple release groups (to manage different products' release schedules), you can view each of these release plans in turn, switching between several saved views on the Roadmap. Or you can use an additional "Roadmap bucket"release group that spans all products to display their features on a single Roadmap view.

Managing multiple products across several projects

For organizations with distinct product offerings with discrete user bases, and unique product prioritization processes for different products

Benefits of using multiple productboard projects:

  • Granular user permissions – Ensure everyone can only access data for the products that matter to them.
  • Discrete Insights boards – Separate repositories of product ideas, requests, and feedback from colleagues and customers.
  • Discrete prioritization criteria – Everyone only sees data fields like objectives, segments, or drivers that relate to their product.
  • Discrete Features boards – Feature ideas for each product are kept entirely separate.
  • Discrete Roadmaps – Each project has its own Roadmap (or set of roadmaps, if saved views are used).
  • Discrete Portals – Each product has its own Portal.

Additional considerations:

  • Projects are discrete environments – Each productboard project is accessible at a different URL. 
  • Users can be shared across projects – The same productboard user may be invited into multiple productboard projects with a different user role in each project.
  • It's easy to switch between projects – Once logged in to productboard, users who are members of multiple projects can seamlessly switch between them using the project switcher in the main menu.

Limitations of using multiple productboard projects:

  • With multiple projects, it won't be possible to get a single unified portfolio view of the Roadmap for all your products. (You will be able to easily toggle between their roadmaps however.)
  • Compared to setting up SSO for a single project, there may be more management overhead to managing multiple productboard projects in parallel.
  • You'll need to set up processes in your organization to ensure feedback for different products gets sent into the correct productboard project.
  • Any ideas, requests, or feedback from customers/colleagues that relate to multiple products will have to be sent into both projects.

Learn more

Looking for more info? Reach out to a member of our team at hello@productboard.com.

Did this answer your question?