Organizations & Teams

You already have one organization and one team. This page is how other people get in — and how you add another team without creating a second account. Invite a teammate, add an organization administrator, or spin up a client workspace next to your own.

What you can do

You already have one organization and one team from Getting Started. Picture Maya's homepage hero sitting in Production on Maya's Team. This page is how other people get into that workspace — and how Maya adds another team without creating a second account.

Two everyday jobs:

Invite a teammate onto the team you already have. A designer should open the same hero Maya is building. You add them on the team, they accept, and you put them on the groups that unlock the composer.
Add a second team in the same organization. A client needs their own widgets, media, and members. You create that team next to Maya's Team. One account. One organization. Isolated work.

You can also invite someone as an organization administrator so they can create teams and invite other org admins. That is a different door from team membership — they will not open the composer until they are on the team too.

How organizations and teams think

The nest you already know still holds: organization → team → project → environment. Getting Started created the first of each. This page is about people and extra teams.

Organization. The account-level container. You administer the one you created. You can invite other org admins. You cannot create a second organization for yourself.
Team. Where day-to-day work lives. Members, permission groups, media, and component libraries belong to the team. Widgets live in an environment on that team.

Here is the case that surprises people. You invite a colleague as an organization administrator. They accept, and Your Orgs shows the org with Manage Org. They can create a client team. They still cannot open Maya's homepage hero. Org admin is not team membership, and it does not grant composer groups. Until they are an active member of Maya's Team — and on a Widget Access group — the composer stays closed.

Each team is isolated: its own members, media, and widgets. An image you upload for Maya's hero is not on the client team. Tokens and published widgets stay on the environment you created them in — see Projects, Environments & Tokens.

Invite a teammate onto the workspace

This is the first complete path: someone new can open the team and, after you assign groups, work on the hero. You need a Team Members group at Manage or Admin — View can see the list but cannot add people.

From the dashboard, open the team under Your Teams with Go to Team.
Open the Team Settings tab. On the Team Members card, click Add Member. (The members list also has Invite Member — same form.)
Enter their Email and First Name. Last name is optional. Submit with Add Member.
They appear on Team Members as Not joined yet. That is a pending invitation, keyed to that email.
They sign in with the same email. If they do not have an account yet, they create one and accept the license — Getting Started covers that. Their dashboard lists the team under Your Teams with Accept Invitation.
They click Accept Invitation. The membership becomes Active, and they land on the team. They can open the team page. They still cannot compose until you put them on groups.
Back on Team Members, open their row. Under Manage Permissions, check the groups they need —Widget Access (View / Manage / Admin) to work on the hero, Media Assets to upload, and so on. Save by ticking the boxes; each one applies as you click.

That is a safe stop. They refresh, open Production, and the Default Widget is there for them too.

Invitation and request-access are different jobs. Add Member creates a pending card they accept on the dashboard. Request-access is for someone who opened a team URL they are not on — they see Team Access Required and click Request Access. You review that on Requests to Join, not on the members list.

An agent can send that same invitation, see the groups, and approve a request to join, after you connect MCP. The walkthrough is on People.

Add an organization administrator

Reach for this when someone should create teams or invite other org admins — not when they only need to edit widgets.

From the dashboard, open the org under Your Orgs with Manage Org.
On the Org Administrators card, click Add Admin, or open View Admins and click Add Administrator.
Enter their email, first name, and optional last name. Submit with Add Administrator.
Their row shows Invitation Pending. They sign in with that email. Their dashboard has an Org Administrator Invitations card with Accept Invitation.
After they accept, the org appears under Your Orgs. They can manage teams and invite other admins. They are still not on Maya's Team until you invite them there too.

Create another team

Same organization, new workspace. Use this for a client, a second brand, or any work that should not share members or media with Maya's Team. You already created the first team in Getting Started — do not run Get Started again.

Open the org from Your Orgs → Manage Org.
On the Teams card, click Create Team.
Type a Team Name a colleague would recognize — “Acme homepage”. Description is optional. Names must be unique inside the organization, ignoring case.
Click Save. You see Creating your team. This can take a couple of minutes... then the same verification and resource screens Get Started uses.
You land in Production on the new team. A Default Widget is already there — Production only, same as the first workspace. Development and Staging start empty of widgets. You are an active member, on every group, so you can build immediately.

When you reach for it

The first path above is invitation. These are the other levers, named as jobs.

What you need	When you reach for it
Pending vs Active	Team members show Not joined yet until they accept, then Active. An Inactive member (or Access Inactive on the dashboard) has a join date but cannot use the team. Org admins show Invitation Pending until they accept.
Request Access	Someone opened a team URL they do not belong to. They see Team Access Required and submit Request Access. You open Team Settings → Requests to Join → View Requests, then Accept Request on Team Access Requests. That creates or activates their membership. It is not the Add Member path.
Manage Permissions	On a member's page. Groups are listed by category — Team Members, Widget Access, Media Assets, Component Libraries, and the rest — usually as View / Manage / Admin. Invited members start with none. The person who created the team starts on all of them.
One account, one self-created org	Joining other people's teams does not use up that slot. If they have not created their own org yet, the dashboard still shows Create Your Workspace or Create Your Own Workspace. Extra teams you add live in the org you already have.
Wrong email	Invitations match the email you typed. A signup with a different address will not see Accept Invitation. Invite the address they actually use, or have them request access.

How this fits

Organizations & Teams is who can walk in, and how many teams share one account. It does not replace a widget, and it does not issue a token. Widgets are what you build. Projects, Environments & Tokens is how a site asks for them. Media and component libraries stay on the team you just invited people into.

Invite the designer. Put them on Widget Access. Open the hero together. Add the client team when that work needs its own walls.