Skip to main content
Orbit AI organizes your work into workspaces. Each workspace has its own projects, agents, automations, and settings. You can switch between workspaces, create new ones, and join existing workspaces using an invite token. The workspace switcher is the central place to manage your team context. The app includes the following main navigation areas. The exact placement of controls can vary by screen size and app version.
Some menu items are plan-, role-, or deployment-dependent. Agents and Automations navigation may return to the main app rather than opening a separate screen when the feature is not currently available in that deployment.

​
Switch and manage workspaces

1

Open the workspace switcher

Use the workspace switcher in the shared app shell to see the workspaces you belong to.
2

Select a workspace

Click a workspace to activate it. Your selected workspace is remembered per device and stored locally in your browser.
3

Create or join a workspace

Where available, choose the option to create a new workspace or join one using an invite code. Invite availability and role assignment depend on your workspace policy.
Your accessible workspaces depend on your membership and role. Workspace membership and invite behavior are controlled by backend policy. Exact invite expiry and role rights may vary.

​
Workspace switcher details

The workspace switcher helps you find and organize your workspaces.
  • Use the search field to filter your workspace list.
  • Favorites and recently used groups help you find common contexts quickly.
  • The active workspace affects which team-scoped records or analytics appear. Before creating or changing a team resource, verify that the intended workspace name is selected in the app header.
If the list is empty, sign out and back in once, check your connection, and ask the workspace owner to confirm membership. Do not assume an empty list means the account or workspace data has been deleted.

​
Create a workspace

1

Open the switcher and choose Create workspace

Click the workspace switcher, then select Create workspace.
2

Fill in the workspace details

Enter a workspace name. The form also supports an icon, slug, description, visibility, industry, and team-size fields.
3

Review visibility

Review the visibility choice carefully. The available values are private, invite-only, and public. The actual sharing consequences depend on backend policy and should be checked with your administrator.
4

Submit and confirm

Submit the form and wait for confirmation. If the request fails, check the entered values and your permissions before retrying.

​
Join a workspace with an invite token

1

Request an invitation

Ask a workspace owner or administrator for an invitation token through an approved channel.
2

Open the switcher and choose Join workspace

Click the workspace switcher, then select Join workspace.
3

Enter the invite token

Type the invite token and submit.
4

Select the workspace

If joining succeeds, select the workspace from the switcher if it is not already active.
Do not post invite tokens publicly. Token expiration, allowed roles, and reuse rules are managed by backend policy and may vary. If you receive an invalid or expired error, request a newly issued invitation from the workspace owner.

​
Projects, agents, and automations guidance

The repository contains project, agent, automation, mission, and deployment-related pages or backend functions. They are not all separately reachable from the current route table. The main navigation’s Agents and Automations links, along with /automations, /agents, /mission-control, and /missions/:missionId, currently redirect to /app. This indicates a routing or availability mismatch in the current source. If you need these features, check with your workspace admin for the supported entry point in the active deployment. Where a project-building surface is enabled:
  1. Open Build Projects or the project workspace.
  2. Describe the goal, platform, user needs, and constraints in plain language.
  3. Review the generated plan before asking for implementation.
  4. Work through changes in small steps and inspect generated artifacts before downloading or using them.
  5. Save or reopen the project through the Library if the feature provides that action.
Where agent or workflow tools are enabled:
  • Use an agent for a bounded task with a clear outcome.
  • Use an automation only when you understand its trigger, permissions, and expected side effects.
  • Review inputs and connected services before authorizing an execution.
  • Inspect run status and any approval request before continuing.
  • Stop a run if it is acting on the wrong workspace or has an unexpected effect.

​
Troubleshooting

If your workspace list is empty after signing in, refresh the page or ask an admin to confirm your membership. If automations fail to load, verify that you have selected the correct workspace and that your account has the required permissions.