> ## Documentation Index > Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt > Use this file to discover all available pages before exploring further. # Organizations and subsidiary workspaces > Create subsidiary workspaces, appoint organization administrators, and grant access separately in each workspace. An organization groups the Neo workspaces owned by an MSP. For example, Acme Corp MSP can manage its own workspace and an acquired MSP's workspace under one organization. Each workspace keeps its own members, roles, agents, integrations, data region, and billing. Existing workspaces receive an organization with the same company name. Active workspace owners become organization owners during the initial migration. Workspace admins do not automatically become organization administrators. If your workspace has no owner, contact Neo to assign an organization owner. ## Organization roles | Role | Permissions | | --------------- | --------------------------------------------------------------------------------------------------------------------------------- | | Owner | Create workspaces, grant workspace access, rename the organization, and appoint or remove organization administrators | | Admin | Create workspaces and explicitly grant workspace access up to Admin | | Neo super admin | Manage organizations and create workspaces for a selected organization; transfer existing workspaces after ownership verification | 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 Open [**Organizations**](https://dashboard.neoagent.io/organizations) from the account menu. Search for and select the organization that owns the subsidiary, then open the **Workspaces** tab. Select **Create workspace**. Enter its name, timezone, PSA, and data region. You can use the Microsoft directory connected to another workspace in this organization or connect a separate directory later. Neo opens the new workspace's plan page. Each subsidiary requires its own paid plan. Its integrations and credentials start separately; Neo does not copy another workspace's PSA or RMM credentials. Invite people 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](https://dashboard.neoagent.io/organizations?tab=administrators) 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. Neo verifies ownership, selects the destination organization, and confirms the transfer. Existing workspace memberships and billing remain unchanged. The destination 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 sets up a separate paid plan. Creating an organization or 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](https://dashboard.neoagent.io/organizations?tab=activity) records creation, role changes, workspace access grants, directory connections, and transfers. It displays the latest 100 events. The public API provides organization administration for signed-in Microsoft users under `/public-api/organizations`. Workspace API keys can read only their current parent organization through `GET /public-api/organizations/current`; 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.