Best Practices for Team Accounts

This article is intended as a quick reference for best practices when working with a team account in Coiled. For more detailed information on the creation and features of team accounts, please see the Documentation page.

Use the account= keyword argument when creating clusters

When spinning up clusters, it is important to include the account kwarg pointing to the team account that you are a member of. This will give your cluster access to all the configured limits of the team account as well as consolidate billing. Failing to include this will cause the cluster to be constrained by the limits of your own personal Coiled account, as well as use up your personal cloud credits.

Update your Cloud Backend Options to use your organization's resources

By default, your clusters will be created using Coiled's AWS account. If your organization has set up its own AWS/GCP account or custom Registry for software environments, it is recommended to configure your Cloud Backend Options to match that of your team account or other members to allow more control of your network and resources. Cloud backend Options can be accessed from your Coiled Profile page or via the Python API.