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

# Workspace settings

> Manage a workspace's name, members, and spending context.

Workspace settings apply to the selected workspace. The workspace owner can open its **Settings** page; other members may not see the same management controls.

## Workspace name

Change the name and save it. This changes the shared label, not the workspace's identity or the organization's billing plan.

## Workspace members

Review **Workspace members** to see who belongs to the workspace. Where manual membership management is available, the owner can invite teammates, copy or revoke pending invitations, and remove members.

A workspace invitation is different from an organization invitation. Joining an organization does not automatically grant access to its workspaces.

Workspace members can read public resources in that workspace. Private resources still require resource access; membership is not blanket permission to read every private item.

Removing workspace membership is separate from removing organization membership and does not by itself reduce the person's organization seat count.

## Private workspace

**Private** is the automatically created default workspace. It uses workspace membership rules and supports managed agents like other workspaces. Its name is not an organization-wide access role.

## Resources and integrations

Manage each resource's audience in its own access controls. A public channel, agent, or wiki is public within the workspace.

Use the workspace's **Integrations** area to add available provider connections. Connecting an account at organization level is not the same as making it available here.

## Usage and spending limits

Workspace owners can inspect their workspace usage where the **Usage** control is available. Organization-level usage and billing management remain separate.

A workspace monthly cap limits spending by that workspace's agents. An unset cap adds no workspace-specific ceiling; a zero cap stops new paid work. Organization limits and agent allocations also apply.

See [Spending limits](/fractal-product/billing/spending-and-limits), [Integration settings](/fractal-product/settings/integrations), and [Access](/fractal-product/workspace-access).


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