Show nav
Heroku Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
  • 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
View categories

Categories

  • Heroku Architecture
    • Dynos (app containers)
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Command Line
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery
    • Continuous Integration
  • Language Support
    • Node.js
    • Ruby
      • Rails Support
      • Working with Bundler
    • Python
      • Background Jobs in Python
      • Working with Django
    • Java
      • Working with Maven
      • Java Database Operations
      • Working with the Play Framework
      • Java Advanced Topics
    • PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
    • Kotlin
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
    • Heroku Redis
    • Apache Kafka on Heroku
    • Other Data Stores
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
    • Compliance
  • Heroku Enterprise
    • Private Spaces
      • Infrastructure Networking
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
    • Single Sign-on (SSO)
  • 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
  • Collaboration
  • ›
  • Collaborating with Other Developers on Your App

Collaborating with Other Developers on Your App

Last updated 17 March 2016

Table of Contents

  • Collaborator permissions
  • Add collaborators
  • View collaborators
  • Remove collaborators
  • Merging code changes

This article shows app owners how to share their app with collaborators.

If you are a collaborator, see Getting Started as a Collaborator.

Collaborator permissions

Collaborators can perform any action that an owner can, except collaborators can not:

  • Add or remove paid add-ons
  • Delete, transfer or rename the app
  • View invoices

These are the only actions that are restricted. Collaborators can perform any other action that an owner can, including scaling applications.

Add collaborators

Other developers can be invited to collaborate on your app by their email address.

$ heroku access:add joe@example.com
Adding joe@example.com to myapp collaborators... done

To use the dashboard to add a collaborator:

  1. Select the app in the dashboard.
  2. Click the Access tab.
  3. Click the Add collaborator button.
  4. In the New collaborator window, type their email address.
  5. Click Save changes.

When you invite a collaborator, an email is sent to let them know they were granted access to the app. If no existing Heroku account matches the email specified, an invitation email is sent.

View collaborators

Use the heroku access command to see the list of current collaborators:

$ heroku access
=== theirapp Collaborators
adam@example.com owner
joe@example.com  collaborator

Remove collaborators

You can revoke a collaborator’s access using the heroku access:remove command:

$ heroku access:remove joe@example.com
Removing joe@example.com from theirapp collaborators... done

To use the dashboard to remove a collaborator:

  1. Select the app in the dashboard.
  2. Click the Access tab.
  3. Click the “x” beside the collaborator’s email address.
  4. Click Delete Collaborator.

Once access has been revoked, the user is no longer able to deploy changes or modify the app’s configuration.

Merging code changes

When you’re collaborating with other developers, you might be prevented from pushing to the repo and see a message like this:

$ git push heroku
error: remote 'refs/heads/master' is not a strict subset of local ref 'refs/heads/master'.
maybe you are not up-to-date and need to pull first?

This means that other developers have pushed up changes that you need to pull down and merge with your local repository. The easiest way to do this is to run git pull --rebase. Ensure your changes don’t conflict with what you pulled down before deploying.

Keep reading

  • Collaboration
  • Getting Started as a Collaborator

Feedback

Log in to submit feedback.

Getting Started as a Collaborator

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Blog
  • Podcasts
  • Support Channels
  • Status

Language Reference

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

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing

Subscribe to our monthly newsletter

  • 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
  • Facebook
  • Instagram
  • Github
  • LinkedIn
Heroku is acompany

 © Salesforce.com

  • heroku.com
  • Terms of Service
  • Privacy
  • Cookies