Spaces and roles

Each team its space, each person their rights

A space gathers a team's agents, files, connections and members. Everyone has a role in it: who builds, who runs, who watches.

A structure that follows your org chart

The organization sets the common frame, each team works in its space, each person holds a role there.

Your organizationModelsToolsRoles
Sales space
Agents · 2
  • Lead qualification
  • Quote follow-up
People · 3
  • Julie M.Admin
  • Marc D.Builder
  • Sophie L.Viewer
Support space
Agents · 2
  • Ticket triage
  • Reply drafts
People · 3
  • Karim B.Admin
  • Léa P.Operator
  • Paul R.Viewer
Finance space
Agents · 2
  • Invoice follow-up
  • Payment matching
People · 3
  • Inès T.Admin
  • Nora S.Builder
  • Marc D.Viewer
  1. The organization

    The shared frame: who is a member, which models and tools are available, which roles exist.

  2. Spaces

    One space per team or department: its agents, its connections, its schedules and its log.

  3. People

    One role per space, from admin to viewer. You can also define your own roles.

Roles

The right access for everyone, checked before you grant it

Five ready-made roles fit most teams. When none does, you create your own by ticking permissions, then look at the app through that person's eyes.

  • A Runner launches agents without seeing their instructions; a Viewer looks without launching anything.
  • "New space role": an identifier, a description, permissions. Custom roles are part of the Apache 2.0 code.
  • "Preview a role" shows the app as that person will see it, with a banner to exit the preview.

Connections

The team's accounts, used the way you decided

When an agent acts in QuickBooks or Outlook, it goes through a connection. The admin decides who can create one, which ones are used by default and which ones a sensitive agent must use.

  • "Users allowed to create a connection": organization administrators, or all workspace members.
  • Default or enforced connections for the whole space, and "Agent-specific connections" for one agent.
  • "Exactly these connections" keeps personal accounts out. Members see "Pinned by an admin" and cannot remove it.

What it changes

For your teams

  • One menu to move from "My space", which is private, to your teams' spaces.
  • You see what concerns your team, without the noise of other departments.
  • You try an agent in your personal space without disturbing anyone else.

For the organization

  • Permissions checked before they are granted, thanks to role preview.
  • Sensitive accounts stay under control: an agent only uses the connections you planned.
  • An invited contractor only enters the space they were added to.

Frequently asked questions

How do I add someone to a space?
"Add a member", in the space's members: a user already in the organization, or a new person, who then joins as a guest with access to that space only. The invitation goes out by email if a mail server (SMTP) is configured; otherwise you copy the link and pass it on. For an existing member: "Restore default role" or "Remove access".
Open, closed or private: what is the difference?
An open space welcomes organization members with the "Role for automatic access". A closed space is visible, but you must be added to enter. A private space is visible and accessible only to the people added to it.
Who administers every space?
Organization owners and administrators are Space admins everywhere. Organization roles (Owner, Administrator, Member, Guest) are fixed; space roles can be extended with custom roles.
Are custom roles paid?
No: they are part of the Apache 2.0 code, like the five ready-made roles.
What is the personal space for?
Every member has "My space", a private space to prepare or try an agent before offering it to their team.
How do members sign in?
With email and password, magic link, Google or GitHub. Enterprise SSO (SAML, Microsoft Entra) is coming soon, with the Enterprise license.

Let's see what it would look like on your side.

Try it on your own in a few minutes, or take thirty minutes with us to scope a first use case.

To try it

Try it for free

Create a cloud account and describe your first agent.

For a guided start

Let's talk about your case

Thirty minutes with us to scope a first use case and its gain.

To audit

Read the code

Apache 2.0. Your technical team can read it all, install it all, keep it all.