Components, templates, design and tools for agentic work Private alpha · free for now

Your agency. Every client in it.

An agency works in workspaces it owns. Each workspace has its own members and roles, and one client list that every app in the suite shares. The people at a client can be invited as guests to see the work you share with them, and nothing else.

Workspaces the agency owns. One chip to switch.

A workspace holds a team, its clients and its work. One account can belong to several, with a different role in each, so the workspace chip in the bar says whose workspace you are in and switches between them. Switching reloads to the app's front page, so no screen is left showing the workspace you just left.

  • The chip lists every workspace you belong to, with your role in each
  • New workspace, Members and Workspace settings are in the same menu
  • A workspace is Solo or Agency. Making it an agency adds client records and guest invitations, and cannot be undone
  • The plan, invoices and billing email belong to the agency, and its owners manage them in Billing

Members, with one role each. Invited by email.

Members see the workspace in every app. Owners and admins invite people by email with a role, change roles and remove people. Anything that takes access away asks first, and a removal shows what the person holds and who it goes to.

  • Owner: everything here, including deleting the workspace
  • Admin: manage members, clients and settings
  • Member: work in this workspace in every app
  • Viewer: see everything, change nothing
  • Clients: a member or viewer can be limited to some clients. With no limit they see every client. Owners and admins are never limited
  • Invitations: the link stays good for 14 days, and can be withdrawn before then

Invite people

Role
Inviting someone with a role. A member or viewer can be limited to some clients; with none ticked they reach every client. The drawing is the Members screen. The invite form takes an email address and a role — Owner: everything here, including deleting the workspace; Admin: manage members, clients and settings; Member: work in this workspace in every app; Viewer: see everything, change nothing. For a member or viewer it lists the clients they can be limited to. Sending adds the invitation, valid for 14 days, to the Invitations list with the clients it reaches.

One client list. Every app reads it.

A client is a company the workspace works for. The Hub, Terminal and Baselumen all read the same list, so a client added in one is there in the others. Open a client and its profile shows what each app holds for them, with a button that goes and does the next thing there.

  • Statuses

    Lead, Active, Paused, Archived.

  • Tabs

    Overview, Files, Brand, Contacts, Sites, Work, Activity, Access and Settings.

  • Baselumen's card

    Counts the collections, component copies and audits filed to the client.

  • Archiving

    Revokes open guest invitations and withdraws pending approval requests. Restoring brings the client back as it was.

Open a client. See what each app holds.

A client's profile gives its health score and its details, then one card for each app in the suite saying what it holds for that company, each with the next thing to do there.

Guests see their own work. Nothing else.

Someone at a client can be invited, from that client's Access tab, to see that company's work from their own sign-in. They are guests, invited read-only: they take no seat, have no role and never appear on Members. Client portals were retired into this on 7 October 2026.

  • Guests see the client's published sites and designs, and the work you turn Share on for
  • They talk to your team in the client channel, never the team-only one
  • Files and Brand are shared with them: they read the brand kit and can send you logos, guidelines and files
  • Owners and admins invite guests and end their access. Guests are told when it ends
From a guest
Up to 50 MB a file
From the team
Up to 100 MB a file
Refused
Programs and scripts, by name and first bytes
Downloads
A short-lived link, never shown as a page

How access is decided. Two layers, checked every time.

The role decides what kind of access a person has. Everything else on this list keeps that access to the right workspace and the right client.

Two layers
A person's role in the agency decides what kind of access they have. For anyone confined to a client, a second check decides which client. Belonging to the agency alone never opens another client's records.
The workspace on the screen
Every change a shared screen sends carries the workspace it was drawn for. If you switched workspace in another tab, the change is refused and the screen reloads, so a tab left open never acts on the wrong workspace.
Guests stay guests
An account that is only a client's guest is sent to the page that shows what was shared with it, not into the agency's screens. Joining a team or choosing a workspace of its own takes the guest view off.
Staff access
Stacklumen staff can open a workspace they are not a member of only by giving a reason, which is logged, and only for a limited time. While they are in it, the workspace chip shows a Staff tag with the time left.
Roles in a workspace
4
Client statuses
4
Client lists
1, every app
An invitation lasts
14 days

Bring the team and the clients in.

Baselumen is in private alpha: billing is not switched on, so a signed-in agency uses all of this for free.