Adding a group or organization as collaborators


One problem we constantly have is, someone in our organization creates an application and forgets to give the rest of us access (or gives it only to one or two people). This means that when the person goes on vacation (or leaves the company) no one else is able to access (we have had problems with the 2 people who have access being on vacation simultaneously).

Is there a way to grant access to a whole organization or a group of people? Even better would be not to have “collaborator” access, but for all of them to be owners.


Hi Mario,

We are working on more powerful tools for organization management as we speak, which should help a lot with this. We don’t have a specific release date for that yet, but I’d expect it to be available within the next few months. That should solve your problem in general by allowing you to all create applications within the organization itself, and providing access to the entire team in a more structured manner.

In the meantime, we typically see customers manage their accounts using a primary billing user, who owns every application (either creating them there, or having other developers move their applications to that user) and who is associated with your billing plan, and then having everybody else added as members to those applications. The billing user’s account can then be managed independently of the developers themselves, and the credentials for that can be managed centrally somewhere to avoid issues where a specific team member is on holiday. Does that work for you in the short term?

Any news on this? It’s becoming more and more annoying to have people in our organization sending messages to be added to this or that application.

Any news on this? It would be really helpful for us, also in light of a shared password being—strictly speaking—in violation of our IT security rules.



Hi @rkuhn and @mario , we are actively working on this and the API model changes are nearly done. Its a priority feature for us this year but requires some initial internal changes before anything can be surfaced externally.

@rkuhn in response to the single shared password issue, are you not using the “member/collaborator” feature to add your team to applications? Its definitely not recommended to use/share a single account.

The issue lies with creating projects and adding collaborators—that can to my knowledge only be done by myself at this point, so bus factor = 1.

That’s a good point @rkuhn - in fact this is one of the planned features coming with the new organizations support Shaun mentioned. There will be an organization owner role that will be able to create applications and assign members, similar to how it works on GitHub.
Before this lands, in the meantime, you could use some third-party password sharing solution, like Passpack , 1Password or Hashicorp Vault in this situation.

Thank you for your feedback !