Team management
Teams allow you to group together databases and share them in a structured form. All accounts begin with a personal team which you are not able to add other administrators or managers. All database instances live within a team. Teams are free to create, but require a credit card to be set up.
To create a new Team, click on the arrow next to the current Team and select "Create New Team".
Managing team access
From the team settings, you can manage user access by clicking on the "Members" navigation link. Each user added to your team receives a role. Default roles are:
- Administrator
- Manager
- Member
- View
Team administrators have all the functionality of managers as well as:
- Manage team members
- Use certain features, such as the Heroku migrator tool
Team managers have all the functionality of members as well as:
- Provision and deprovision instances
- Create and respond to support tickets
- Configure settings for Postgres clusters
- Create and manage saved Queries
- View and update billing
- Receive email notifications about cluster availability
- View data insights
Team members can:
- See database resources and information
- Create a Postgres role in a database with a connection string
View role:
- Limited read access to Crunchy Bridge dashboard and databases
Custom access groups
Under team settings you'll find a tab called Access Groups. This panel allows the creation of custom groups and permissions that can be applied to one or more users who have permissions to one or more clusters.
When creating a new access group, you'll need to choose:
Cluster permissions
- Admin
- Manage
- Fine-grained, including creating Postgres role, viewing or managing queries, or viewing Insights
Team permissions
- Admin
- Manage
- Fine-grained, including manage billing
Scope
Once you have defined the Cluster and Team permissions, you can define the new access group's scope as to which clusters and which team members it will apply. The default will be All clusters and All members, or you can choose a subset.
Access group examples
- A billing role that can only see invoices but no clusters or other members
- A group for managing a specific group of clusters within a single billing account
- Administrators that can only administer a group of other members, rather than all members
- A group of members who can see Insights or manage Queries