Open your organization
Open Organization from the account menu. The page shows the organization of the workspace you have open, with its workspaces on the Workspaces tab. Any member of the workspace can view this list. The organization is the root of the tree, and each workspace shows its status, data region, and your access. The Administrators and Activity tabs, the Create workspace button, and access grants need an organization role. To look at another organization, open one of its workspaces first. This applies to Neo staff too.Organization roles
Organization administration does not itself grant access to workspace data. On the Workspaces tab, use the workspace’s three-dot menu and select Grant workspace access… to give yourself or another existing member an explicit workspace role. A workspace you cannot open also shows a Grant access… button. Only organization owners can grant the workspace Owner role. The person who creates a new workspace becomes its workspace owner.
Removing an organization role leaves that person’s workspace memberships unchanged. To remove all access, remove the organization role and revoke each workspace membership. Neo prevents removal or demotion of the last organization owner.
Create a subsidiary workspace
1
Open the parent workspace
Switch to a workspace of the organization that will own the subsidiary, then open Organization from the account menu and stay on the Workspaces tab.
2
Create the workspace
Select Create workspace at the top of the Workspaces tab. Enter the workspace name and its workspace ID, then pick the timezone, PSA, and data region. The workspace ID is the unique lowercase identifier Neo uses for the workspace, as at signup: letters, digits, and hyphens. Neo fills it in from the name; edit it if you want a different one. The ID is permanent; the name can change later. An ID that another workspace already uses is rejected. You can use the Microsoft directory connected to another workspace in this organization or connect a separate directory later.Under Invite owners, you can add the email addresses of up to 10 people who should own the new workspace. Neo skips your own address, because you own the workspace already. Each other person gets an email invitation, valid for 7 days, and accepts it by signing in with Microsoft. After Neo creates the workspace, it shows which invitations it queued. Neo sends the emails in the background. If a person gets no email, or an invitation could not be queued, invite that person again from the new workspace’s Users page; the workspace is created either way.
3
Start a trial or choose a plan
Neo opens the new workspace. It can start its own free trial, or you can choose a paid plan for it from the start. A new workspace gets no Teams support chat of its own; its people get help from the Neo Support agent in the dashboard. Its integrations and credentials start separately; Neo does not copy another workspace’s PSA or RMM credentials.
4
Invite its team
Invite everyone else from the workspace’s Users page with their name, work email, and role. They accept the email invitation using Microsoft sign-in. Invitees gain access only to this workspace.
Microsoft directories and sign-in
A workspace can have its own Microsoft directory or share one with other workspaces. Sharing a directory does not give its employees access to every connected workspace. Neo checks each person’s active workspace memberships after sign-in. One accessible workspace opens directly. People with several memberships can switch workspaces, with their role shown separately in each. The switcher also shows the workspace’s organization. For a separate directory, a workspace owner from that company opens Microsoft directory in the account menu and selects Connect my Microsoft directory. Neo uses the directory of their verified sign-in; nobody needs to enter directory or object IDs. Each Microsoft integration still needs its own consent and setup. Contact Neo to change an existing directory connection. Workspaces connected to the same directory use the same external Microsoft resources. Neo keeps its workspace records and credentials separate. The existing limit of one branded Teams bot installation per Microsoft directory still applies; use the dashboard to select among multiple workspaces.Add organization administrators
Invite a person to a workspace first. After they accept, an organization owner can open the Administrators tab and select Assign administrator. Choose the person and their Owner or Admin role, then select Save organization role. A pending invitation cannot receive organization authority.Bring an acquired MSP into the organization
Contact Neo to move an existing workspace into your organization. Neo verifies ownership and makes the change. Existing workspace memberships and billing remain unchanged. Your organization’s administrators can then explicitly grant access. An invitation between companies does not move a workspace or establish an ownership relationship. A shared email domain, Microsoft directory, or Stripe customer does not establish ownership either.Billing
Each new subsidiary has its own free trial and its own paid plan. Moving a workspace does not combine Stripe customers, subscriptions, credit balances, or invoices. Existing billing arrangements remain in place. Consolidated organization billing is outside this release.Audit and API access
The Activity tab records creation, role changes, workspace access grants, and directory connections. It displays the latest 100 events. The public API provides organization administration for signed-in Microsoft users under/public-api/organizations. GET /public-api/organizations/current returns the organization of the workspace in X-Client-Id; the other routes accept only that organization’s ID. Workspace API keys can read only their current parent organization; they cannot create subsidiaries, change organization roles, or grant cross-workspace access. Neo Support can explain these actions and direct an administrator to the dashboard.