---
title: Orgs & teams
description: Shared workspaces on hosted ggui — the pooled org wallet, the owner/admin/member role model, the email invite flow, and how an org is dissolved.
---

An org is a shared workspace with a pooled credit wallet. Members you invite render against the org's wallet, so nobody needs their own balance topped up individually, and a single coupon can credit the whole team.

Orgs live at `/orgs` in [the ggui console](/hosted/console/). Every org you belong to is listed there — the ones you created and the ones you were invited into — badged with your role.

:::note[Orgs are not hosting]
An org shares a wallet, a member list, and org-scoped blueprints. Production agent hosting and shared operational dashboards belong to **guuey**, the separate agent-hosting platform built on the same protocol.
:::

## Creating an org

Give it a name and confirm. Left blank, it is created as "My ggui org". You are its first owner.

## Roles

Every membership carries one of three roles.

|                                 | member | admin | owner |
| ------------------------------- | ------ | ----- | ----- |
| Render against the org wallet   | yes    | yes   | yes   |
| See the wallet balance          | yes    | yes   | yes   |
| Redeem a coupon into the wallet | yes    | yes   | yes   |
| Invite members                  | no     | yes   | yes   |
| Rename the org                  | no     | yes   | yes   |
| Remove a member                 | no     | yes   | yes   |
| Remove an admin                 | no     | no    | yes   |
| Change someone's role           | no     | no    | yes   |
| Dissolve the org                | no     | no    | yes   |

Anyone can leave an org on their own — an owner only once a second owner exists, so an org is never left ownerless. For the same reason the last remaining owner cannot be demoted; promote someone else first.

Owners cannot remove other owners directly. Demote them to admin or member, then remove them.

## Inviting people

Owners and admins invite by email from the org's detail page, choosing the new member's role (member or admin). The recipient gets an email with a one-time accept link.

That link is the credential. The invite id in the URL is what authorizes the claim — anyone signed in who holds the link can accept it, and it is not matched against the recipient's email address. Send it to the person, not to a channel.

Invites expire, and pending ones are listed on the org page with their target email, role, and expiry, each with a **Revoke** action. Inviting the same address twice reuses the existing pending invite rather than issuing a second one.

Following the link lands the recipient on `/invites/[inviteId]`. If they are not signed in they see the sign-in form first; once authenticated the invite accepts itself and drops them straight into the org.

## The org wallet

Each org carries its own wallet, shown on the org page with the current balance alongside lifetime granted and lifetime spent. Any member can see it.

Credit reaches an org wallet through coupon redemption: on `/credits`, the redeem form offers your personal wallet or any org you belong to as the destination. Personal balances and org balances are separate ledgers — see [Credits, billing & BYOK](/hosted/billing/) for how charges are priced.

## Members

The member list shows each person's display name or email, their role, and when they joined. Owners change roles inline from that list. Removing someone takes effect immediately; your own row offers **Leave** instead.

## Dissolving an org

An owner can schedule dissolution from the org's danger zone. The org is deleted after a seven-day grace period, and any owner can cancel during that window. While it is scheduled, the org shows a `dissolving` badge in the list and a banner on its detail page.