Collaboration intro

# An account is for personal access

Most people are running multiple apps on fortrabbit, commonly under different contexts (agency, private, client). The classical approach is to set up a new account for each project. Then the account is shared with colleagues and clients. That's hard to manage and not professional. The fortrabbit collaboration concepts are designed as a better alternative.

Sign up to fortrabbit as an individual, not a company. In fact the account is part of the person object. Mind that your personal public SSH keys are also stored with your account.

Note that only people are actively interacting with the dashboard, anything else is an object to be accessed and controlled by people.

# Build for trust

The fortrabbit collaboration features are build to enable productive co-creation. The purpose is to connect people working together as developers and their business owners within the hosting platform. It's not about fine grained access control.

The collaboration features are a powerful sword aimed for professional usage. It's anticipated that you have trust and policies in place within the context of your real word relations and teams to avoid misusage and damage.

# Many to many relations

The fortrabbit collaboration features are designed without a lot of hierarchy. This enables to map many types of real world scenarios. You can have multiple apps, payment methods and teams connected to your personal account. Apps can be connected to multiple teams and solo developers. Payment methods also can be connected to multiple individuals and teams.

# Co-ownership

Apps are paid and thus owned by payment methods, not accounts. People with access on the payment method have billing control. Payment methods can be shared with developers, clients and teams. See the billing collaboration article for more.

# Use cases

• Solo developers working for clients directly
• Solo developers working for organizations
• Smaller organizations with a fixed team
• Bigger organizations with multiple teams

# Example workflows

• Invite clients and non-devs to take over billing
• Create teams to share apps with other developers
• Pass over app access from developer to developer

# Two levels of collaboration

There are two types of collaboration on the fortrabbit hosting platform:

• Developer collaboration - sharing technical aspects
• Billing collaboration - sharing billing access

This enables to share developer access to an app without sharing billing access at the same time. It's also the foundation to work with non-technical business owners (clients).

With teams it's practical that the unlimited members have combined control on developer access and billing access.