Department based
A standing Space for a function that runs the same work every week — marketing, finance, legal, operations, or support.
- Lifespan
- Ongoing
- Members
- Function lead + specialists
- Examples
- Finance operationsLegal reviewIT service desk
Spaces are purpose-built operational environments where your people and agents come together in shared context. Configure your capabilities once, and every piece of work in the Space draws on them automatically.
When organizations start deploying agents, they run into the same challenge: agents, knowledge, and capabilities end up configured separately for each use case. Teams repeat the same setup. Context becomes inconsistent. Access is hard to manage.
Spaces solve this by giving every team, project, or initiative a single coordinated environment — where agents, knowledge, tools, and guardrails are set up once and shared across everything that happens there.
Agents, knowledge, and capabilities end up configured separately for each use case. Teams rebuild the same foundation over and over instead of reusing what already works.
When every agent carries its own configuration, the same question gets different answers depending on which agent picks it up and how it happens to be set up.
Permissions scattered across individual agents and documents make it difficult to know who can see what — and harder still to change it as teams evolve.
A Space is an operational environment in Opal that brings together everything a team needs to work with agents. You set it up once — and every piece of work inside draws on it.
The digital workers that do the work inside the Space — collaborating in Threads, running Tasks, and executing Flows alongside your team.
Shared information that grounds everything happening in the Space, so people and agents work from the same source of truth.
Capabilities that extend what agents can do — added at the Space level and available to every agent operating there.
Policy boundaries that keep every agent and workflow in the Space within the rules your organization sets.
Team members added with permission levels matched to their role — Manage, Access, or View.
The work itself. From within the Space, people and agents collaborate in Threads, run Tasks, and execute Flows — all drawing on the same shared resources.

When you add a Connector, Tool, Skill, Widget, or Guardrail to a Space, it becomes available to every agent and every piece of work in that Space. You configure it once. It carries through.
This is how operational consistency works at scale. One policy. One integration. One knowledge source. Applied wherever it's needed — without repeating setup for each agent.
Agents, knowledge, capabilities, and work all live in a single environment. Teams stop assembling context from scattered tools and start working from a shared foundation.
Add a Connector, Guardrail, Skill, or Tool to a Space and it becomes available to every agent and workflow in it. No repeated setup. No configuration drift.
Three permission levels — Manage, Access, and View — give each person exactly the right level of involvement. Team leads manage settings and sharing. Specialists edit and use the Space. Stakeholders follow along.
Because agents, guardrails, and knowledge are attached to the Space, every Thread, Task, and Flow runs from the same foundation. Outputs stay aligned. Behavior stays predictable.
A Space can be organized around a department, project, customer, initiative, or product. Structure reflects reality — not the other way around.
There is no fixed model. Most organizations start with one or two Spaces and expand as more teams come on. These are the common shapes we see — mix them however your work is organized.
A standing Space for a function that runs the same work every week — marketing, finance, legal, operations, or support.
A Space that mirrors an existing team, holding the agents, knowledge, and guardrails that team relies on day to day.
One Space per customer or account, so context, documents, and access stay cleanly separated between clients.
A dedicated home for a defined piece of work with a start and an end, archived once the project ships.
A Space built around a company-wide push that spans several teams — a launch, a compliance program, or a transformation.
Manage, Access, and View give every member exactly the right level of involvement — set at the Space level and applied to everything inside it.
Guardrails configured on a Space apply across every agent, Thread, Task, and Flow that runs there. Policy is set once, not per agent.
Changes to a Space's agents, knowledge, and capabilities are tracked, so teams can see what changed and when.
Opal does not retain prompts or outputs at the model level. Work inside a Space stays within your organization's data boundary.
Membership changes, permission updates, and configuration events inside a Space are logged as a complete, reviewable record.
ISO 27001, ISO 42001, and SOC 2 Type II certifications are underway.
Set up your first Space in minutes and see how Opal brings your people, agents, and work into one shared context.