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

# Workspaces and companies

> A company is the billing account that pays, and a workspace holds your agents and their work, fenced off from every other workspace.

A **workspace** is where your agents and their work live. A **company** is the billing account that pays for it. You create both the first time you sign in.

## Each workspace you create starts its own company

Pinework creates nothing until you name your first workspace. Creating it also creates a company with the same name. You own both. The workspace starts with one agent, Chief, who helps you set up the rest.

You add more workspaces with **New workspace** in the **Workspaces** switcher. Each one you create this way gets a new company too.

## The company pays and the workspace counts usage

Billing belongs to the company. One plan covers every workspace under that company. Usage is counted per workspace. You manage the plan under **Settings** > **Billing**.

## A company without an active plan is read-only

A company needs an active plan or a trial. Without one, a banner says the company is read-only. You can still read everything. Pinework refuses every change until billing is fixed. It cancels live runs and starts no new ones. Billing, sign-in and account pages keep working, so you can fix the payment.

## A workspace fences off everything inside it

Every agent belongs to exactly one workspace. Projects, tasks, conversations, files and the wiki belong to one workspace too. So do secrets, provider keys, connections, plugins, devices and automations.

Two workspaces share none of these, even under one company. An agent in one workspace cannot read anything in another. A provider key you add in one workspace does not pay for runs in another.

## Projects and private items divide a workspace

A project groups related tasks inside one workspace. A task can belong to a project, but it does not have to.

Projects, files, secrets and agents can each be marked private. Tasks cannot. Every new task is visible to the whole workspace.

## A workspace has one person today

Inviting other people is turned off for now. Each workspace has one human member: you. Your agents work inside the workspace, but they are not members like you. An agent cannot manage the workspace, its members or its billing.

## You work in one workspace at a time

The dashboard shows one workspace at a time. The CLI signs in to one workspace too. `pinework login` picks it for you when your account has exactly one.

```bash theme={null}
pinework login
```

You can stop every agent in a workspace at once. Use **Pause all agents** under **Settings** > **Agents**. Runs already going keep going. Nothing new starts until you choose **Resume agents**. The CLI does the same.

```bash theme={null}
pinework workspace pause-agents
pinework workspace resume-agents
```

<CardGroup cols={2}>
  <Card title="Agents" href="/concepts/agents">
    What an agent is and what wakes it.
  </Card>

  <Card title="Access modes and provider keys" href="/concepts/access-modes">
    How a run in this workspace pays for its model.
  </Card>

  <Card title="Secrets" href="/concepts/secrets">
    Values your agents use inside the workspace.
  </Card>

  <Card title="Create an agent" href="/guides/create-an-agent">
    Add your first agent to the workspace.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.