Skip to content

Organizations and workspaces

Everything in Lainstack lives in a workspace, and every workspace belongs to an organization. This page is for anyone setting up Lainstack for a team, and for authors who want to know where their work lives.

Level What it holds Where to manage it
Super organization The top level. People who oversee several organizations, single sign-on, domains and security policy such as requiring SSO. Settings, under the super organization
Organization Your company or team. Its members, teams, roles and OAuth clients. An organization lives in one region, and so do its workspaces. Settings, under the organization
Workspace The work itself: automations, connections, reference tables, operations, runs, escalations and agents. Members of a workspace see only that workspace’s work. The workspace and its Workspace Settings
Each level contains the next. Your work lives in workspaces; people, teams and access are managed above them.

Creating an organization also creates its super organization and a first workspace, so a new account starts with one of each.

The left rail of a workspace has two groups:

  • Build: Automation, Connections and Data Lake. This is where you put the machinery together.
  • Operate: Operations, Runs, Escalations and Agents. This is where you watch and steer the work that runs.

Workspace Settings sits at the bottom of the rail, with General (the workspace name) and Members. Switch workspaces from the workspace switcher at the top.

  1. Open Workspaces and click New workspace.
  2. Enter a Workspace name and a Slug. Lainstack adds a short number to the slug to keep it unique.
  3. Click Create workspace.
The Workspaces directory of an organization, with the New workspace button.

You become the workspace’s Workspace lead. Creating a workspace needs the Organization admin or Operations director role. The workspace is created in the organization’s region; there is no region choice per workspace. The organization and slug are fixed once the workspace exists, and only the name can change later.

Each level has its own roles, and people can hold a role at more than one level.

  • Super organization: Operations director, Finance & compliance, Network viewer, Support (audited), External auditor.
  • Organization: Organization admin, Finance & compliance, Organization viewer, Organization member, Support (audited), External auditor.
  • Workspace: Workspace lead, Workspace operator, Workspace runner, Workspace viewer, Guest collaborator, Workspace auditor.

Roles and what they allow are managed in the organization settings under Access & Roles.

People join by invitation only. Nobody is added to an organization without accepting.

The Members page with the Members and Invited tabs and the Invite button.
  1. Open Members at the level you want: super organization, organization or workspace.
  2. Click Invite, then choose the person, their Role and, if the access should end, Access expires on.
  3. Click Send invitation.

The rules differ by level:

  • Organization and super organization invitations go to an email address. An invitation link is valid for 7 days. The Invited tab lists pending invitations, with Resend, Revoke and Copy link.
  • Workspace invitations go to a current organization member, or to an email address. Someone new gets one invitation that adds them to the organization and the workspace together, if the inviter can also manage the organization’s members.

The person reviews the invitation, sees the role they are offered, and chooses Accept invitation or Decline. Pending invitations also wait under Personal, in Invitations.

Hierarchy, regions and isolation covers who can invite at each level, what each invitation gives, and what keeps organizations and workspaces apart.

Teams group organization members, for example to assign escalations to a group instead of one person. Create them in the organization settings under Teams with Create team. A team member is either a Member or an Owner. Archiving a team can be undone.

Last updated: