Account organization

# Best use one account only

A fortrabbit account maps to a person in real life. People manage apps, teams, and payment methods.

# How NOT to handle one account

• No account sharing please - No need to create an account and share credentials with colleagues or clients. Use collaboration features.
• No generic accounts please - Please sign up with firstname.lastname@company.com and not accounts@company.com.

# Why to have multiple fortrabbit accounts

In some scenarios it might be advisable to have multiple accounts at fortrabbit as one individual:

# Strict separation

Collaboration features are designed to be open and transparent. Collaborators can see your other apps, payment methods, and teams on your profile. They can see names and metadata, but cannot access them. Often that is desired; this way you can request access to an app that you need to work on as well.

If you don't want to expose any of your other projects to your co-workers, create a second private account at fortrabbit.

# Multiple GitHub accounts

At GitHub you can also use one Account to manage personal repos, contribute to other people's repos, and be part of multiple organizations. But when you have multiple accounts at GitHub, maybe one for work and a private one, you may also want to keep that separation with fortrabbit.

# GitHub connection limits

• You can't connect the same GitHub account to multiple accounts at fortrabbit
• You can't connect multiple GitHub accounts to one account at fortrabbit

# How NOT to handle multiple accounts

• New account for each app - NO! You can have multiple apps
• New account for new trial - NO! Each new app starts as a new trial
• New account for each client - NO! Use client collaboration
• New account for organization - NO! Use developer collaboration