Set up your organization

The first setup steps for an organization admin, in order: invite people, put a team in a user group, give the group a workspace, make that workspace the default, check the roles, and add a connector. At the end, everyone in the team can work in the right workspace from their first sign-in.

All of these steps are in Settings. What you see there depends on your role and your deployment. Owners and admins see the organization and Admin sections; Members see fewer items.

Admin setup: invite a new hire, group people, give the group a workspace and make it the default, read Roles, install a connector (1:25).

Invite people

1. Go to Settings > Members and click Invite. Only people who can manage members see it (owners and admins by default).

2. In Invite people, type or paste email addresses, separated by commas. You can paste up to 500 at once.

3. Pick a role. Member is preselected:

   Role	Description in the dialog
   Member	Can use agents and create workspaces
   Admin	Can manage members, agents, workspaces, and settings
   Owner	Can do everything, including billing

   You can’t give someone a role higher than your own, so an admin can’t invite an owner.

4. Under Workspaces, pick the workspaces they should join. This is optional: with none picked, new people land in the organization’s default workspace (see Set the default workspace).

5. Click Send invite.

The person waits in the Invited list, with a role such as “Member (Invited)”, until they accept. An invitation expires after 7 days. Expired invitations stay in the list marked “(Expired)”; use Resend in the row’s menu to send a new one, which starts a fresh 7 days. To cancel a pending invitation, choose Revoke invitation.

Agents are also listed on Members, in their own Agents group.

Create a user group

A user group is a saved list of people. Give the group access to something once, and everyone in it gets it, including people you add to the group later.

1. Go to Settings > Members > User groups and click Create user group.
2. Name it, for example “Advisory team”, and click Create user group. The group’s page opens.
3. Click Add people and add each person. The page shows the count, for example People · 4.

A group can contain people and agents, but not other groups. Groups synced from your identity provider show “Synced from …” and are managed there, not by hand.

User groups are available only on organizations that use the newer permissions system, and only to people who can manage the organization’s settings and members (owners and admins by default). Without it there is no User groups tab.

Give the group a workspace

1. In Settings > Workspaces, open the workspace, for example Northwind Advisory, and go to its Members tab.
2. Click Invite. In Add to workspace, search for the group; it is marked User Group.
3. Pick the workspace role, such as Member (“Read, write, and run workspace resources.”) or Viewer (“View chats and shared workspace items without sending chats or editing resources.”), and click Add to workspace.

Everyone in the group now has that role in the workspace, in one step. The group is listed in the workspace’s members with access Direct; people who reach the workspace through the group show an inherited access label instead. What each workspace role can do is on Roles.

Set the default workspace

The default workspace is “Where new people land: invited without a workspace, SSO, and email-domain sign-ups. One setting for all of them.”

1. Go to Settings > Workspaces.
2. Under Default workspace, choose Find a workspace… and pick one, for example Northwind Advisory.

The checklist under the field shows what uses it: Invites, SSO and Email domain. The deployment’s setup console reads the same setting. If no default is set, new people who weren’t invited to a workspace wait until an admin invites them. Only people who can manage the organization’s settings (owners and admins by default) can change it.

Check what each role can do

Go to Settings > Roles: “What each role in the organization can do. Owner always has everything.” The Org roles tab shows Owner, Admin and Member against each area:

Area	What it covers	Owner	Admin	Member
People	Invite and manage members and owners	Yes	Partly: not owners	No
Billing	Plans, payment and invoices	Yes	No	No
Settings & security	Org settings, security policy, delete or transfer the org	Yes	Partly: not the security policy, deleting or transferring	No
Workspaces	Create, delete and administer every workspace	Yes	Partly: not administering every workspace	Partly: create
Agents	Create and manage org agents	Yes	Yes	No (yes for creating agents on the newer permissions system)
Skills & applets	Manage skills and applets, publish to the org catalog, approve applets	Yes	Yes	Partly: not approving applets
Evals	Open Evals	Yes	Yes	No

In short: only owners handle billing, admins can invite people and create agents, and members get some workspace and skill rights. The Workspace defaults tab sets the workspace roles (see Roles), and Share levels sets the roles used when sharing.

The Roles page appears only on organizations that use the newer permissions system, to people who can manage the organization’s settings. Only the Owner can change roles. The full matrix is in the Roles matrix.

Install a connector

Settings > Connectors decides what your organization can plug in. Turning a connector off there hides it everywhere in the organization and stops agents using it.

1. Click Install connector. Only people who can manage the organization’s settings see it.
2. Choose how people sign in: Personal (“Each person signs in with their own account.”) or Team (“One shared key every agent uses.”).
3. Under Server address, paste the server’s https address. Context checks how it signs in, for example “No sign-in needed.”
4. Check the Name and click Install connector. More options has the rest of the settings.

When it says “[Connector] is ready”, everyone in the organization can use it. To narrow that, choose Choose who can use it. In the list, the switch On for [organization] turns it off everywhere with one click, and turning it on never reaches further than the deployment allows.

Some deployments show a newer Connectors page, with different wording (for example Connector and Team account when you install). The steps are the same. How connectors sign in, which workspaces get them and where they can reach are in Connectors.

Next steps

• Workspaces: who creates workspaces, adding people automatically, and closing a workspace.
• Workspace settings: who can join a workspace and what can be shared across it.
• Sign-in options: single sign-on, so new people land in the default workspace.