Account organization

# One account at fortrabbit is preferred

No need to create an account and share credentials with colleagues or clients. A fortrabbit account maps to a person in real life. Please sign up with firstname.lastname@company.com and not accounts@company.com.

Only people act; everything else is an object. One account lets you manage multiple apps, teams, and payment methods.

This maps to the way GitHub is organized. At GitHub you can have your personal repos, contribute to other people's repos, and be part of multiple organizations.

# How NOT to handle one account

• Share one account with multiple people - Collaboration rules!

# Why NOT have multiple fortrabbit accounts

• New account for each app - You can have multiple apps, with individual billing
• New account to start a new trial app - Each new app starts as a new trial
• New account for each client - Client collaboration is much better
• Creating an account for your agency - Developer collaboration is much better

# 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.

# You have multiple GitHub accounts

When you have two accounts at GitHub, maybe one for work and a private one, you may also want to keep that separation with fortrabbit.

# GitHub connection limits

The connection between a fortrabbit account and a GitHub account is 1:1. That means:

• 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