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

# Workspace

> Configure your workspace—company details, API access, sandboxes, and more.

Your workspace is the top-level container for everything in Plane. It holds your team, payroll runs, documents, settings, and integrations. When you sign up for Plane, your workspace is created automatically. Most configuration happens at the workspace level, so understanding what lives here helps you keep things organized as your team grows.

## General settings

Workspace settings are available from the **Settings** section of the sidebar. The general settings let you configure your workspace name, which appears throughout the Plane interface and in communications to your team.

To update your workspace name, navigate to **Settings > Workspace** and edit the name field. Only admins can modify workspace settings.

## Company information

Your company information is tied to the organization within your workspace. This includes details that Plane uses for compliance, payroll, and legal documents:

* Company legal name
* Address and jurisdiction
* Employer identification numbers and tax IDs
* Funding source for payroll and payments

Setting up company information accurately is important because it flows into tax filings, employment agreements, and payment processing. Navigate to your organization settings to review and update these details.

<Note>
  Some company information fields are locked after your first payroll run because they are tied to regulatory filings. Contact support if you need to make changes to locked fields.
</Note>

## Sandboxes

Sandboxes let you test Plane's features without affecting your live data. A sandbox creates a separate test workspace linked to your primary workspace. You can use it to experiment with API integrations, test onboarding flows, or explore features before rolling them out.

Each sandbox:

* Has its own workers, payroll, and settings—completely isolated from your live workspace
* Is automatically provisioned when created
* Can be named for easy identification (Plane generates a default name if you do not provide one)

Navigate to **Developers > Sandboxes** to create and manage your test environments.

<Tip>
  Sandboxes are especially useful when building API integrations. You can test your integration against the sandbox workspace before pointing it at production. See the [API reference](/reference/introduction) for details on authenticating against sandbox workspaces.
</Tip>

## Multiple workspaces

Each Plane account can have access to multiple workspaces. This is useful if you manage separate legal entities or business units that need independent payroll and team configurations.

Each workspace operates independently with its own:

* Workers and organizational structure
* Pay schedules and bank accounts
* Documents, compliance, and settings
* API keys and integrations

You can switch between workspaces from the workspace selector in the sidebar. The workspace you are currently viewing determines which data and settings you see.

## API access

Plane provides a REST API for programmatic access to your workspace data. API keys are scoped to a single workspace and are managed from **Developers > API keys**.

### Managing API keys

<Steps>
  <Step title="Create an API key">
    Navigate to **Developers > API keys** and click **Create key**. Give the key a name that describes its purpose (for example, "HRIS sync" or "Payroll automation").
  </Step>

  <Step title="Copy the key">
    The full API key is shown only once at creation time. Copy it and store it securely. Plane stores only the key digest, so the plaintext key cannot be retrieved later.
  </Step>

  <Step title="Use the key">
    Include the API key in the `Authorization` header of your API requests. See the [API reference](/reference/introduction) for authentication details.
  </Step>
</Steps>

<Warning>
  API keys provide full access to your workspace data. Treat them like passwords—store them in a secrets manager, never commit them to version control, and rotate them if compromised.
</Warning>

To revoke an API key, navigate to **Developers > API keys**, find the key, and delete it. Deletion takes effect immediately.

## Webhooks

Webhooks let Plane push event notifications to your systems in real time. Instead of polling the API for changes, you register a URL and Plane sends HTTP POST requests when events occur—like a worker being onboarded, a payment being processed, or a payroll run completing.

Webhook configuration is managed from **Developers > Webhooks**. Plane connects to an external management portal where you can configure endpoints, select event types, and view delivery logs.

For details on webhook event types and payload formats, see the [API reference](/reference/introduction).

## Permissions

Workspace settings are restricted by role:

* **Admins** can view and modify all workspace settings, create API keys, manage sandboxes, and configure webhooks
* **Viewers** can view workspace settings but cannot make changes
* **Managers and workers** do not have access to workspace settings

<AccordionGroup>
  <Accordion title="Can I rename my workspace?">
    Yes. Navigate to **Settings > Workspace** and update the name. The change applies immediately across the Plane interface.
  </Accordion>

  <Accordion title="Is sandbox data completely separate from my live workspace?">
    Yes. Sandboxes create a fully isolated test workspace. Workers, payroll runs, and settings in a sandbox do not affect your live data.
  </Accordion>

  <Accordion title="How many API keys can I create?">
    There is no hard limit on the number of API keys per workspace. Create as many as you need for different integrations and services, and delete any that are no longer in use.
  </Accordion>
</AccordionGroup>