Skip to main content

How a dbt account is structured

This page shows how a dbt platform account is organized. Some things, like git and single sign-on (SSO), you set up once for everyone. Others, like environments, you set up inside each project.

Think of your account as an office building. The front door and security desk are shared by everyone. Each team gets its own floor with its own rooms.

The account: what you set up once, and the projects that share it.The account: what you set up once, and the projects that share it.
Inside a project: the repository, connection profiles, and environments.Inside a project: the repository, connection profiles, and environments.

What lives where​

The following table shows where you configure each part of your account.

LevelWhat you set up hereHow many
AccountGit integrationOne per git provider
AccountSingle sign-on (SSO)One per account
AccountUsers, groups, and permissionsDefined once, then scoped to projects
AccountSecurity and networkingDefined once
AccountWarehouse connectionsAs many as you need
ProjectRepositoryOne per project
ProjectConnection profilesAs many as you need
ProjectEnvironments and jobsOne development environment, plus deployment environments

Common mix-ups​

These are the things that trip people up most during setup.

  • You don't need a project per environment. A project isn't "dev" or "prod". Each project can have a development, staging, or production environments. Create a new project when you have a separate codebase or team, not a separate stage. Refer to types of environments for more information.
  • Integrations are set up once per account. You connect your SSO identity provider once at the account level, and you can’t set a different one for each project. With Git, you can connect each git provider application once for the account (for example, an account supports one GitHub application), and each project then chooses its own repo. Projects in the same account can use different providers, such as GitHub for one and GitLab for another, and more than one project can use the same repository.
  • Warehouse connections belong to the account, not the project. Any project can reuse a connection. A connection only reaches a project when you attach it to one of that project's environments.
  • Connection profiles belong to the project. A profile bundles one connection with deployment credentials and extended attributes. Profiles you create in one project aren't visible in others, and they don't apply to development environments.

Environments in a project​

Each project has the following environment types.

Environment typeHow many per projectWhat it's forShows in Catalog
DevelopmentOne at mostBuilding in the Studio IDE or dbt platform CLI with your personal credentialsNo
GeneralAs many as you needDeployment work like QA, sandboxes, or ad hoc runsNo
StagingOne at mostTesting with production tools before changes reach productionYes
ProductionOne at mostScheduled and triggered jobs that build your source of truthYes

For more information, refer to dbt environments and Deployment environments.

More than one data platform​

One account can hold connections to more than one data platform. Each project picks the connection it needs for each environment. Your git, SSO, users, and security settings stay shared across the whole account.

Was this page helpful?

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

0
Loading