Features

Organizations

CloudClawer orgs let a whole team share a single workspace. When you connect your Linear workspace, your schedule snapshots, intake tickets, and cost data become visible to every org member — no more per-person silos.

Organizations require a Linear workspace. If your team doesn't use Linear, org features are not available yet.

Joining an org

Connecting to an org takes a single click once your Linear key is in place.

Go to Settings → Org.
If you have a Linear API key configured (Settings → Linear), click Connect org. CloudClawer resolves your org from Linear automatically — no extra input needed.
On success you'll see your workspace name, provider, admin username, and current member count.

If you don't have a Linear key configured yet, the Org tab will prompt you to set one up first. Head to Settings → Linear to add your key, then return to the Org tab.

Org vs. personal

Not everything is shared. Here's how data is scoped:

Shared (org)

Schedule snapshots (Gantt)
Intake tickets (Tech Tree)

Personal

API keys and secrets
Proxy allowlist
Vault
Routine triggers

The Gantt header shows an org: <workspace>badge when you're viewing an org-shared schedule, so you always know whether you're looking at team data or your own.

Admin and members

The first user to connect a Linear workspace becomes the org admin. Their account is the billing target for all org-level resource usage. Subsequent users who connect the same Linear workspace join as regular members.

An admin badge appears next to the admin username in Settings → Org so the rest of the team knows who to contact. Each CloudClawer user can be admin of one org per identity provider — for example, one Linear org per account.

If your Linear workspace already has members, they can each connect independently to join the org. There's no invite flow — connecting the same Linear workspace is all it takes.

Schedule sharing

When any member computes a schedule on the Tech Tree page, it is stored in the org namespace and immediately visible to all members via the Gantt page. Everyone sees the same snapshot until one of them recomputes — there's no merge or conflict step. This makes the Gantt a shared source of truth for the team's current plan.

Costs

Session costs and PR costs are uploaded per-user, attributed to the individual who ran the session. Each member can view their own spend on the Costs page.

Org-level cost aggregation — a team dashboard view showing combined spend across all members — is planned but not yet available.