Watch the Opal launch video
The Agentic Operations Platform

Give every team a home for their agents and work.

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.

Space · customer successshared context
configured once
available everywhere
agentsknowledgeconnectorsguardrails
threads
conversation
tasks
execution
flows
multi-step workflows
The problem

Agents deployed one at a time never add up.

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.

01

Setup gets repeated for every use case

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.

02

Context becomes inconsistent

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.

03

Access is hard to manage

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.

What is a Space

One environment for everything a team needs.

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.

  1. 01

    Agents

    The digital workers that do the work inside the Space — collaborating in Threads, running Tasks, and executing Flows alongside your team.

  2. 02

    Knowledge

    Shared information that grounds everything happening in the Space, so people and agents work from the same source of truth.

  3. 03

    Skills, Connectors, and Tools

    Capabilities that extend what agents can do — added at the Space level and available to every agent operating there.

  4. 04

    Guardrails

    Policy boundaries that keep every agent and workflow in the Space within the rules your organization sets.

  5. 05

    People and permissions

    Team members added with permission levels matched to their role — Manage, Access, or View.

  6. 06

    Threads, Tasks, and Flows

    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.

Space · input → outcomeone environment
input
people
webhooks
systems
the Space
shared foundation
agents
people
knowledge
skills & tools
working in
threadstasksflows
guardrails
policy check
output
governed outcome
traceable · on policy · on standard
Inside a Space

Every thread, task, flow, and knowledge source in one place.

Opal Space overview showing flows, tasks, threads, knowledge, and recent activity
Configure once

Configure once. Available everywhere.

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.

Without Spaces
research
connectorguardrailskillknowledge
drafting
connectorguardrailskillknowledge
review
connectorguardrailskillknowledge
publish
connectorguardrailskillknowledge
setup repeated per agent4 × 4 = 16 configs
With Spaces
one configuration
connectorguardrailskillknowledge
researchinherits all 4
draftinginherits all 4
reviewinherits all 4
publishinherits all 4
shared across every agent4 configs total
Key benefits

Shared context that compounds over time.

Everything in one place

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.

Configure once. Share across the Space.

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.

Controlled access

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.

Consistent context across all work

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.

Built around how teams actually work

A Space can be organized around a department, project, customer, initiative, or product. Structure reflects reality — not the other way around.

Ways to set up Spaces

Structure your Spaces around how you actually work.

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.

Setup 01

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 operations
Legal review
IT service desk
Setup 02

Team based

A Space that mirrors an existing team, holding the agents, knowledge, and guardrails that team relies on day to day.

Lifespan
Ongoing
Members
Whole team
Examples
Demand generation
Support escalations
Recruiting ops
Setup 03

Client based

One Space per customer or account, so context, documents, and access stay cleanly separated between clients.

Lifespan
Life of the account
Members
Account team + stakeholders
Examples
Acme Corp account
Northwind renewal
Contoso onboarding
Setup 04

Project based

A dedicated home for a defined piece of work with a start and an end, archived once the project ships.

Lifespan
Duration of the project
Members
Cross-functional project team
Examples
ERP migration
Website relaunch
Data center move
Setup 05

Initiative based

A Space built around a company-wide push that spans several teams — a launch, a compliance program, or a transformation.

Lifespan
Duration of the initiative
Members
Sponsors + contributing teams
Examples
SOC 2 readiness
Product launch
Cost reduction program
Security and governance

Governance set at the Space, inherited by everything.

01

Three permission levels

Manage, Access, and View give every member exactly the right level of involvement — set at the Space level and applied to everything inside it.

02

Inherited guardrails

Guardrails configured on a Space apply across every agent, Thread, Task, and Flow that runs there. Policy is set once, not per agent.

03

Versioned configuration

Changes to a Space's agents, knowledge, and capabilities are tracked, so teams can see what changed and when.

04

Zero Data Retention

Opal does not retain prompts or outputs at the model level. Work inside a Space stays within your organization's data boundary.

05

Audit Log

Membership changes, permission updates, and configuration events inside a Space are logged as a complete, reviewable record.

06

Certifications

ISO 27001, ISO 42001, and SOC 2 Type II certifications are underway.

Spaces

Build organized, governed environments for every team.

Set up your first Space in minutes and see how Opal brings your people, agents, and work into one shared context.