Organisations

Organisations, at /orgs.

"Teams that operate stores together. Adding someone here does not open any store — a store's owner attaches it from their own settings."

That second sentence is the whole model, and it runs against most people's intuition. Reading it properly saves you a confused afternoon.

Four steps, in this order

The screen itself lists them:

1. Create the organisation and name your team. Whoever creates it is the owner.

2. Invite colleagues by email. The invitation appears in their notification bell and has to be accepted — "inviting opens no store by itself."

3. The store's owner goes to that store's Settings → Agency, picks the organisation and attaches it. "That is the only step that grants access."

4. After step 3 every member can see and work on that store — including people added later.

Step 3 is the one that gets skipped. People create the organisation, invite the whole team, then wonder why nobody can see any stores. Because no store has been attached to the organisation.

Why it is two steps

An organisation answers "who is on my team". Attaching answers "which stores may that team run".

Merge them and adding somebody to the team would open every client store to them — with the store owner having no say. Kept apart, the store owner keeps the decision, and the agency can still manage its own staffing without asking permission every time it hires.

Three roles in an organisation

Role	vi
Owner	Chủ sở hữu
Admin	Quản trị
Member	Thành viên

"Members reach every store attached to this organisation — and none that are not."

That is a clean boundary: an organisation's reach is exactly the list of stores attached to it, and nothing more.

Pending invitations

The Invited, not yet answered area shows people invited but not yet joined: "They are not in the organization until they accept."

You can Withdraw an unanswered invitation at any time.

Removing someone

Remove a member: "{email} will lose access to every store this organisation operates."

This is the model's strongest point: removing somebody from the organisation cuts their access across all client stores at once. No walking site by site.

Leaving

Leave organisation — "You lose access to every store {org} operates. Someone still in it would have to invite you back."

There is no way back on your own. Make sure somebody else is still in it before you leave.

Transferring ownership

Transfer ownership hands the owner role to another member. "The new owner takes over managing members. You stay on as an admin."

You are not pushed out — you step down one level.

Deleting an organisation

Delete organisation removes it and everyone in it, and cannot be undone.

But there is a guard:

"Give back the {n} store(s) this organization operates before deleting it."

You cannot delete an organisation that is operating other people's stores. You have to Give back each store first — otherwise those stores would lose their operator without their owners knowing.

Stores this organisation operates

The Stores this organisation operates area lists them, each with Open and Give back.

Give back is the agency's side of ending an engagement. The store owner can do the equivalent from their side — see Moving sites around.

New store, above the list, creates a store already attached to the organisation: "It is created and attached to the organization in one step — no need to make it in your own dashboard first." For a store the agency builds from scratch, that is one step instead of two.

Shared sections

Below the stores is Shared sections: "Sections your stores have offered each other. Approved ones appear on every store's Templates shelf." A store in the organisation can offer a section it built; an owner or admin approves it, rejects it with a note the author reads, or later takes it down. The section templates themselves are described in Elements and traits.

Organisations versus a site's team

Do not confuse the two lists:

• Organisations (/orgs) — your team, spanning many stores.
• Team (Manage → Team) — the members of one store. See Team and roles.

A store can have both at once: the owner's own staff, plus an agency attached to operate it.

Apps belong to organisations too

If you build apps, an app is published by an organisation rather than by a person: the Developer portal entry on this page opens it. With no organisation, the developer portal says so immediately: "Apps belong to an organisation." See Build an app.