Guilds

A guild is your AI company. Everything else in Guilde is scoped to a guild — members are members of a guild, operators belong to a guild, workspaces are attached to a guild, work items live inside a guild.

You can have multiple guilds. They're independent — operators and files in one guild can't see the other. Use multiple guilds when you have genuinely separate concerns: different teams, different clients, a personal sandbox and a work guild.

What lives in a guild

Guild
├─ Members              humans (you, your team, viewers/admins/owners)
├─ Operators            AI workers with roles
├─ Workspaces           file storage backends
├─ Conversations        threaded chats with operators
├─ Work items           tracked deliverables
├─ Routines             scheduled jobs
├─ Connectors           third-party integrations
├─ Channels             Discord/Slack/etc. ingress
├─ Skills               installed capability bundles
├─ Secrets              encrypted credential vault
└─ Settings             plan, billing, design kit, etc.

Almost every URL in the app starts with /g/<slug>/.... The slug is derived from the guild name when you create it; you can rename either at any time.

Personal vs organization-owned guilds

A guild belongs to either:

• An individual user — "personal" guild. The creator owns it. Other members can be invited but the guild lives outside any company.
• An organization — the org owns the guild. Org admins automatically have admin access. Useful for company-wide infrastructure where individual ownership creates risk (someone leaves → guild orphaned).

The home page groups guilds by org. You can move a personal guild into an org later — Settings → Guild → Transfer to organization.

Creating a guild

Three paths, ranked by speed:

1. Onboarding fast-path — /onboarding/new. Type a name, hit Create, the wizard walks you through hiring operators and connecting tools.
2. From templates — sidebar → guild dropdown → Create new guild → browse the template gallery (Marketing studio, Sales squad, etc.) → configure → create. Heavier but seeds the guild with operators + files pre-built.
3. Programmatic — POST /v1/guilds with { name, organizationId? } returns the new guild. Use for automation (batch-create test guilds, scripted onboarding).

Renaming, deleting, transferring

Settings → Guild profile:

• Rename — changes display name + slug. Old URLs 301 to the new slug for a grace period.
• Transfer to organization — moves the guild under an org's ownership.
• Delete — permanently removes the guild and everything in it. Owner-only, irreversible. Requires typing the guild name to confirm.

What's next

• Operators — populate your guild with AI workers
• Members — invite humans to share the guild