Organization settings

Org-level settings — five tabs covering identity, guilds, members, billing, and org-wide connector credentials.

The Organization settings page (/org/settings) is where you manage the org wrapping your guilds — your company, your agency, a team. It has five tabs:

Settings — org identity (name, slug, contact)
Guilds — every guild owned by this org
Members — org-level members and roles
Billing — shared subscription, payment, invoice portal
Connectors — OAuth credentials and BYOK keys inherited by every guild in the org

Organization settings — Settings tab with Name + URL slug fields, plus sibling tabs (Guilds, Members, Billing, Connectors)

When to use an org

A guild can be personal (owned by you) or org-owned. Use an org when:

Multiple teammates need admin access to multiple guilds
You want central billing across guilds
Credentials (BYOK keys, OAuth integrations) should be shared rather than re-pasted per guild
A guild outlives the person who created it (someone leaves → guild doesn't get orphaned)

The five tabs

Settings — Name, URL slug (agentikstudio.guilde.work), support email, deletion. Mirrors the per-guild Profile page but at the org level.

Guilds — Every guild owned by the org. Create new guilds inheriting org members and credentials. Member counts and last activity per guild.

Members — Org-level membership. Roles applied here cascade across all org-owned guilds. Audit log of joins, role changes, leaves.

Billing — Single subscription that covers all org-owned guilds. Stripe portal, invoice list, plan changes. Per-guild billing is disabled when the guild is org-owned.

Connectors — Shared OAuth integrations + BYOK provider keys. A key registered here is inherited by every guild in the org. Useful for "the team uses one Anthropic API key" without having to re-paste per guild. See Usage → BYOK for the per-guild override.

Org admin permissions

Org admins automatically get admin access to every guild in the org. That's how the company stays in control of its AI infrastructure even as individual guilds come and go.

Creating an org

The sidebar's account section (when not inside a guild) shows Organizations → Create new…. The registration flow asks for org name, slug, contact email; on submit, you can immediately invite members and transfer existing guilds into the new org from each guild's Profile page.

What's next

Members — the per-guild member view
Billing — per-guild billing (disabled when org-owned)
Usage → BYOK — per-guild BYOK overrides