> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# For Admins

> What a Paradime Admin needs to know to set up a workspace for the team, including warehouse connections, git, users, roles, and access controls.

You're the **Admin**: the role that owns workspaces, connections, billing, and users. This page gives you the core of what an Admin needs to know about Paradime, then the setup path to get your team building.

## What Paradime is, for you

Your team gets one platform for the whole dbt™ lifecycle: developing models (Code IDE), AI-assisted engineering (DinoAI), production orchestration (Bolt), and observability (Radar, Catalog, Lineage). Your job is to stand up the workspace they'll do it in.

As Admin, you'll mostly live in **Settings**. The other apps are all available to you, but these are the surfaces you own:

| You manage            | What it controls                                                                            |
| --------------------- | ------------------------------------------------------------------------------------------- |
| **Environments**      | The warehouse connections behind development, scheduled runs, cost tracking, and AI agents. |
| **Git repository**    | The repo that holds your dbt™ project; enables commits and pull requests from the IDE.      |
| **Users**             | Who's in the workspace and which role they hold.                                            |
| **Configuration**     | dbt™ version, environment variables, workspace settings, and SSO.                           |
| **Plans and billing** | Subscription, usage, and audit logs.                                                        |

## Concepts you should know

* **One workspace = one dbt™ project + its connections + its team.** Larger orgs run several workspaces and connect them with data mesh. See [how Paradime works](/guides/foundations/how-paradime-works).
* **Environments keep dev and prod apart.** The Code IDE builds into a development schema; Bolt runs production with separate credentials. Radar uses a read-only cost connection. You'll configure each once. See [environments and connections](/guides/foundations/environments-and-connections).
* **Three roles, one decision per invite.** Admins configure, Developers build, Business users get read-only access to Catalog, Lineage, Radar, and Bolt logs. Most teammates are Developers; stakeholders are Business. See [roles and permissions](/products/settings/users/roles-and-permissions).
* **Everything rides on git.** Paradime never bypasses your review process: developers work on branches and ship through pull requests in your existing repo.

## Your setup path

<Steps>
  <Step title="Create a workspace">
    <Card title="Create a workspace" href="/guides/paradime-101/getting-started-with-your-paradime-workspace/creating-a-workspace" icon="plus" horizontal>
      Name it after the dbt™ project it will hold.
    </Card>
  </Step>

  <Step title="Connect your data warehouse">
    You'll need credentials for a development and a production target. Consider a dedicated service account for scheduled runs.

    <Card title="Set up data warehouse connections" href="/guides/paradime-101/getting-started-with-your-paradime-workspace/setting-up-data-warehouse-connections" icon="database" horizontal>
      Snowflake, BigQuery, Redshift, and more.
    </Card>
  </Step>

  <Step title="Connect your git repository">
    <Card title="Manage workspace configurations" href="/guides/paradime-101/getting-started-with-your-paradime-workspace/managing-workspace-configurations" icon="git-branch" horizontal>
      Git, dbt™ version, and environment settings.
    </Card>
  </Step>

  <Step title="Invite your team">
    <Card title="Manage users in the workspace" href="/guides/paradime-101/getting-started-with-your-paradime-workspace/managing-users-in-the-workspace" icon="user-plus" horizontal>
      Invite users and assign Admin, Developer, or Business roles.
    </Card>
  </Step>
</Steps>

<Check>
  When these four steps are done, a Developer can open the Code IDE and run their first model. Point them to the [Developer quickstart](/start-here/quickstart/for-developers).
</Check>

## Go deeper

<CardGroup cols={2}>
  <Card title="Administration reference" href="/products/settings/index" icon="settings">
    Every setting: environments, git, users, SSO, and configuration.
  </Card>

  <Card title="Integrations" href="/integrations/index" icon="plug">
    Warehouses, git providers, SSO, and the rest of your stack.
  </Card>

  <Card title="Foundations" href="/guides/foundations/index" icon="lightbulb">
    The concept explainers behind the platform.
  </Card>

  <Card title="Migrating from dbt Cloud™?" href="/guides/migrations/dbt-cloud-tm-importer/migration-from-dbt-cloud-playbook" icon="arrow-left-right">
    The migration playbook, checklist, and job importer.
  </Card>
</CardGroup>


## Related topics

- [Admin Dashboard](/products/dino-ai/admin-dashboard.md)
- [Administration](/products/settings/index.md)
- [Power BI](/integrations/power-bi.md)
- [Standard roles and permissions](/products/settings/users/roles-and-permissions.md)
- [Invite users](/products/settings/users/invite-users.md)