Organizations

An organization sits above communities. It's the right structure when one institution, company, or program runs several communities and wants shared administration and a shared credit pool.

What an organization gives you

• Shared admins — an owner or admin of the organization is automatically an admin of every community the organization owns, with no per-community role needed.
• Shared billing — organization-owned communities draw on the organization's credit balance and plan, managed from Settings → Billing with the organization selected. Transferring ownership of an org-owned community does not move its billing.
• Deletion rights — an organization owner can delete an archived community the organization owns.

Managing an organization

Create one at Settings → Organizations (or /organization/new). An organization page has three tabs:

• General — name and settings (managers only; members see that they belong to it).
• Members — managers only for the actions: the invite control and the pending-invitations list are rendered only for an owner or admin, so a plain Member sees the roster and nothing to act on. Roles are Owner, Admin, and Member; invitations default to Member, and managers can promote a member to admin or demote an admin back. Only owners and admins get the shared community admin rights described above.
• Communities — again managers only for the action: a plain Member sees the linked communities but no link button. As a manager you can link an existing community you directly own or administer to the organization. Being an admin only through another organization is not enough here: linking moves the community's billing ownership, so it asks for a direct role on the community itself.

A Billing button in the header opens the organization's billing.