Last updated August 20, 2026
CLI flag names have been upgraded from --org to --team. --org commands are still compatible during this deprecation period.
Developing and deploying applications with a Heroku Team or an Enterprise Team is largely the same experience as doing so in your personal account. Git-based deploys, command-line scaling, and add-ons all behave as expected. However, as with account administration, there are a few additions to the experience to be aware of when working within a team.
Joining a Team
Teams centralize the management of users and roles. To join a Heroku Team or an Enterprise Team, an admin user must add you directly.
After you’re on a team, you can select it in the Heroku Dashboard to view its apps. The Heroku Dashboard shows all teams that you belong to in the sidebar.
Developing Apps
As a member of a team, you have the ability to list and access all apps in the team. You can select an app in the app list to view its basic details, including who can give you more permissions on the app.
You need additional permissions on an app to deploy, scale, work with add-ons, and more. Going to an app’s Access tab shows you what access you have on the app. Team admins and users with manage permission on the app can grant you additional permissions.
In the CLI
To access apps in your team, you can list them by specifying the --team flag:
$ heroku apps --team acme-widgets
=== Apps in team acme-widgets
acme-website
To work with an existing app in the CLI, you must join the app first:
$ heroku join -a acme-website
Joining acme-website... done.
join happens automatically on the Heroku Dashboard.
Leaving an App
When you’re no longer working with an app regularly, you can leave the app. Leaving an app revokes all of your permissions on the app, but you can always select the app again to restore basic view access.
From the CLI, use the leave command:
$ heroku apps:leave --app acme-website
Leaving application acme-website... done
Or, in the Heroku Dashboard, go to the Access tab of the app and remove yourself from the list of members.
Adding Apps to a Team
If you have existing apps you’re developing under your personal account, you must transfer them to your team for them to be considered part of the team and billed against it.
You can use the CLI to transfer apps to your team. In this example, acme-widgets is the team name and deep-spring-4274 is the app:
$ heroku apps:transfer acme-widgets --app deep-spring-4274
Transferring deep-spring-4274 to acme-widgets... done
You can also use the app settings page in the Heroku Dashboard to transfer app ownership.
You can also create apps directly in the team:
$ heroku create --team acme-widgets
Creating frozen-wave-4030 in organization acme-inc...done
http://frozen-wave-4030.herokuapp.com/ | git@heroku.com:frozen-wave-4030.git
Git remote heroku added
Setting a Default Team
The Heroku CLI defaults to using your personal account and requires the --team flag when performing team actions. If you generally work under a particular team, you can set the HEROKU_ORGANIZATION environment variable to default to that team.
$ export HEROKU_ORGANIZATION=acme-widgets
$ heroku apps
=== Apps joined in organization acme-widgets
frozen-wave-4030
salty-depths-3445
The default team doesn’t persist when you open a new shell, however. For that you can add this setting to your profile file. For Unix machines using bash, use ~/.bashrc. For Windows you can set environment variables on the Advanced tab of System in the Control Panel.
Transfer a Team to or from an Enterprise Account
If you have an existing Heroku Team that incurs charges to a payment card, you can transfer the team to your Enterprise account to consolidate billing. You can also request to migrate an Enterprise Team out of your Enterprise account. See Transfer Heroku Teams To and From Enterprise Accounts for more info.