Skip Navigation
Show nav
Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
    • .NET
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Heroku Blog

    Find out what's new with Heroku on our blog.

    Visit Blog
  • Log inorSign up
Hide categories

Categories

  • Heroku Architecture
    • Compute (Dynos)
      • Dyno Management
      • Dyno Concepts
      • Dyno Behavior
      • Dyno Reference
      • Dyno Troubleshooting
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Developer Tools
    • Command Line
    • Heroku VS Code Extension
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery & Integration (Heroku Flow)
    • Continuous Integration
  • Language Support
    • Node.js
      • Working with Node.js
      • Node.js Behavior in Heroku
      • Troubleshooting Node.js Apps
    • Ruby
      • Rails Support
      • Working with Bundler
      • Working with Ruby
      • Ruby Behavior in Heroku
      • Troubleshooting Ruby Apps
    • Python
      • Working with Python
      • Background Jobs in Python
      • Python Behavior in Heroku
      • Working with Django
    • Java
      • Java Behavior in Heroku
      • Working with Java
      • Working with Maven
      • Working with Spring Boot
      • Troubleshooting Java Apps
    • PHP
      • PHP Behavior in Heroku
      • Working with PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
    • .NET
      • Working with .NET
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
      • Migrating to Heroku Postgres
    • Heroku Key-Value Store
    • Apache Kafka on Heroku
    • Other Data Stores
  • AI
    • Working with AI
    • Heroku Inference
      • Inference API
      • Quick Start Guides
      • AI Models
      • Inference Essentials
    • Vector Database
    • Model Context Protocol
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
      • Single Sign-on (SSO)
    • Private Spaces
      • Infrastructure Networking
    • Compliance
  • Heroku Enterprise
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Integrating with Salesforce
  • Extending Heroku
  • Building Add-ons
  • Add-on Development Tasks
  • Create an Add-on "user access list"

Create an Add-on "user access list"

English — 日本語に切り替える

Last updated February 06, 2024

Table of Contents

  • Prerequisites
  • Implementation

To manage users of your add-on, you have at least one login tool set up. Heroku provides the Add-on Single Sign-on integration, which allows users to log in with their Heroku account directly from their app’s dashboard. Some add-ons also have their own login systems, or use third-party OAuth services like GitHub to gain additional capabilities. Having a consolidated list of logins between the Add-on SSO service and your own login system can make managing permissions in your add-on easier.

This article describes how to create a “user access list” by making requests to the Platform API for Partners.

Prerequisites

  • Access to and use of the Platform API for Partners.

Implementation

User List Types

There are two different lists of Heroku users that you must combine to see all users with access to the app:

  • App collaborators are users that an app’s owner has granted access to. These users appear on the app’s collaborators list.

  • Team members for Heroku Teams or Heroku Enterprise Teams appear on the team member list of the team that owns an app.

Get a Full List of Heroku Users

To get a full list of Heroku users with access to your add-on, combine the app’s collaborators list with the team member list. Make these API requests to get the lists:

  • Add-on Info: Use the resource UUID sent on the provisioning request to get the app id or name: GET https://api.heroku.com/addons/:resource_uuid.
  • App Collaborator List: Use the app id or name to get the list of collaborator users: GET https://api.heroku.com/apps/:app_id_or_name/collaborators.
  • App Info: Use the app id or name to check for the existence of a team object on the serialized response to grab the team id: GET https://api.heroku.com/apps/:app_id_or_name.
  • Team Member List: If the app belongs to a team, use the team id: GET https://api.heroku.com/teams/:team_id/members.

If the email address given during the SSO request appears in your combined list, that user has access to the add-on for the specified app.

Repeat this process for each provisioned add-on resource, authenticating with the resource-scoped access token for that add-on under the Platform API for Partner.

The list of app collaborators and team members is dynamic and can change at any time when owners add or remove users from their apps. You must keep the information synchronized by running this process regularly. We recommend using an interval that doesn’t exceed the session expiration time for your add-on dashboard.

Keep reading

  • Add-on Development Tasks

Feedback

Log in to submit feedback.

Writing to Application Logs as an Add-on Partner Implementing Credential Rotations as an Add-on Partner

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure
  • .NET

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing
  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Github
  • LinkedIn
  • © 2025 Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco, CA 94105, United States
  • heroku.com
  • Legal
  • Terms of Service
  • Privacy Information
  • Responsible Disclosure
  • Trust
  • Contact
  • Cookie Preferences
  • Your Privacy Choices