Skip to main content
Back to Integrations
Productboard logo

Productboard

Inventory Productboard members and their roles, so you can see who holds the paid admin and maker seats, which seats belong to people who have left or never use Productboard, the teams people are on, and the Jira sites, plugin integrations and webhooks that send Productboard data to other tools.

Support

Questions you can answer 12

Each one is a saved query that ships with ConfigView, reading your Productboard data on your own server. Ask it in plain English, SQL, Slack or the API.

  • Who has admin rights in Productboard?
  • Who holds a paid Productboard maker seat?
  • When did each Productboard admin last use it?
  • What is connected to Productboard?
  • Where do Productboard webhooks send our product feedback?
  • Which Jira sites is Productboard connected to?
  • Which Productboard makers haven't used it in 90 days?
  • Which Productboard seats could we reclaim?
  • Which Productboard invitations were never accepted?
  • Who has left the company but is still in Productboard?

What ConfigView collects from Productboard 7

  • Jira Integrations

    Jira sites connected to Productboard, which push features into Jira issues and sync their status back: the integration's name, whether it is turned on, and when it was set up.

  • Member Activity

    How much each member used Productboard, day by day: whether they were active, how many boards they opened, and how many notes, insights and features they created. Counts only - nothing they wrote is stored. Kept as a growing history, so it shows who holds a paid seat without using it.

  • Members

    Everyone with access to the Productboard workspace, including disabled members and invitations not yet accepted: name, email, role (admin, maker, contributor or viewer - admins and makers are the paid seats), whether the member is disabled, and the teams they are on.

  • Plugin Integrations

    Outside tools hooked into Productboard's Features board through a plugin integration - a push button that sends a feature to another system: the tool's type and name, whether it is on, and when it was added. The address it sends to and its secret are never returned by Productboard and are not stored.

  • Team Members

    Who is on each Productboard team.

  • Teams

    Productboard teams: name, the @handle used to mention them, and when each was created and last changed.

  • Webhooks

    Webhooks that send Productboard changes (features, notes, releases, objectives and more) to an outside address: which changes are sent and the host they go to. The full URL and its authorization header are not stored.

Back to Integrations