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

# Overview

> How workspaces organize your repositories, integrations, and team in Blocks

A workspace is your isolated environment in Blocks. Everything — repositories, integrations, API keys, skills, and sessions — belongs to a workspace.

## Types of Workspaces

**Personal workspaces** are created automatically when you sign up. They're for individual use and don't support multiple members.

**Organization workspaces** are for teams. They support multiple members, role-based access, and admin-controlled permissions. You can create one during onboarding or anytime using the workspace switcher in the bottom-left of the dashboard.

## What a Workspace Contains

* **Repositories** — connected repos available to all workspace members
* **Integrations** — platform connections (GitHub, GitLab, Bitbucket, Slack, Linear, and others), configured per workspace
* **API keys & environment variables** — credentials used by coding agents running in this workspace
* **Skills** — reusable prompts shared across the workspace, available on all platforms
* **Sessions** — coding agent sessions are scoped to the workspace they were started in

Each workspace is fully isolated. Repositories, skills, sessions, and settings in one workspace have no effect on another.

## Roles

Organization workspaces have two roles:

* **Admin** — full access to all settings; can invite and remove members, assign roles, and configure workspace-wide permissions
* **Member** — access to repositories, skills, and sessions; visibility into settings is determined by admins

### What Admins Control

Admins manage members and roles from **Settings → Members**, and configure workspace-wide behavior from **Settings → Permissions**.

Admins can restrict what members can see:

* Authentication settings
* API keys
* Environment variables
* Integrations
* Analytics
* MCP servers

Admins can also enforce workspace-wide behaviors:

* Force all sessions to be private
* Require members to connect external accounts before accessing the workspace
* Disable VSCode on sessions

## Switching Workspaces

Click the workspace name in the bottom-left sidebar to open the workspace switcher. Selecting a workspace updates the entire dashboard context — repositories, skills, sessions, and settings all switch to that workspace.

<Note>
  Your sessions, settings, and skills are specific to each workspace. Switching workspaces changes your entire context.
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Can't See a Repository">
    **Cause**: Repository not authorized in the GitHub App installation.

    **Solution**:

    1. Go to GitHub → Settings → Applications → Blocks
    2. Add the repository to your GitHub App installation
    3. Refresh the Blocks dashboard
  </Accordion>

  <Accordion title="Can't Access a Team Workspace">
    **Cause**: You haven't been invited, or you don't have a Blocks account yet.

    **Solution**: Create a Blocks account, then ask your workspace admin to send you an invitation.
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="Skills" icon="terminal" href="/using-blocks/features/skills">
    Create shared skills for your workspace
  </Card>

  <Card title="Multi-Repo Support" icon="folder-tree" href="/using-blocks/features/multi-repo-support">
    Work across repositories in your workspace
  </Card>

  <Card title="Getting Started" icon="rocket" href="/using-blocks/getting-started">
    Complete setup guide for new users
  </Card>
</CardGroup>