Skip to main content
A workspace contains one company’s domain anchor, profile, baseline evidence, competitors, documents, signals, connections, members, plan, and credit context.

​
Confirm the active workspace

The Company panel header shows the current company name and domain. Select that block to open the workspace switcher. The selected workspace controls:
  • the route shown in the browser;
  • the workspace identifier sent with product API requests;
  • the profile, documents, competitors, and Analytics data you see;
  • the connection catalog and selected provider resources;
  • member role, plan, billing, and credits;
  • chat and activity history.
Confirm the workspace before starting a correction, changing competitors, connecting a provider, inviting a member, or reviewing billing.

​
Switch workspaces

1

Open the switcher

Select the company identity at the top of the Company panel.
2

Choose a workspace

The current workspace appears first with a check. Select another available workspace.
3

Verify the route and domain

Alesta navigates directly to the selected workspace route. Confirm the company name and domain before continuing.
Open document and competitor tabs close when you switch because those identifiers belong to the workspace that created them.

​
Create a workspace

Select New workspace… at the bottom of the switcher. Enter the company domain, then choose Create. The server validates the domain and can either create a new workspace or resolve an existing workspace that already represents it for your account. The application switches to the returned workspace before it starts polling the baseline. The same domain can exist in different customer accounts. Workspace membership and data do not merge across those accounts.

​
Domainless workspaces

An incomplete workspace with no domain cannot produce a baseline. Alesta opens a domain dialog over the Company screen. If another valid workspace exists, you can dismiss the dialog and switch; otherwise you must attach a domain to continue. A domain submitted on alesta.ai can be carried through signup in a short-lived first-party cookie and attached automatically on the first authenticated load.

​
Keep company context separated

Create a separate workspace when the company, product, audience, domain, members, connections, or billing responsibility should remain distinct. Do not reuse one workspace for unrelated companies. Corrections, accepted competitors, generated documents, and chat context are designed to become shared memory inside that workspace.

​
Workspace safety checklist

  • Check the domain before every external connection.
  • Do not invite a person who only needs another workspace.
  • Keep staging analytics properties out of a production company workspace unless that is the explicit purpose.
  • Reopen generated documents after upstream profile or competitor changes.
  • Include the workspace name when contacting support, but never include credentials or tokens.

​
References