AI agent workspaces: One workspace for every system you run.
A ConvOps workspace keeps one team, product or customer behind its own walls: its own work, workflows and memory. Support, finance, product, a customer. One question still searches every workspace you belong to.
isolated by default · searched together · written to exactly one
How do you keep AI agent work for different teams or customers apart?
One ConvOps workspace per system: its own tasks, workflows, executors, policies and memory, isolated by row-level security in Postgres, yet searchable together by its members.
ConvOps is the operations layer for AI agents. It holds your team's process as workflows with gates, a shared memory, scheduled and unattended runs, programs, a plan board, metrics and a full audit trail. It does not sell or host models.
key facts · october 2026
- Workspace isolation is enforced by Postgres row-level security with FORCE, so a missing filter in one query cannot leak another workspace.
- Recall searches every workspace you are a member of in one query; every write lands in exactly one workspace.
- A new team, product or customer gets its own workspace instead of its own tool.
best for
- Agencies and consultancies running agent work for several clients.
- Companies separating support, finance and product processes.
not for
- Fine-grained permissions inside one workspace. Roles are owner, admin and member.
updated
One shared space for every system.
Support, finance, product and your customers all in one list, one rulebook and one search. Nobody can tell what is theirs.
“Can the customer see our internal work?”
Their tasks sit in the same list as your notes. One wrong filter and they read what they should not.
“Why is support buried in finance noise?”
Every team shares one board, one set of rules and one search. Nobody finds their own work.
“Do we need a new tool for every system?”
A second process means a second tool, a second login and a second place things get lost.
Everything one system needs. Behind one wall.
Each workspace owns its work, its workflows, its rules, where it runs and what it remembers. Nothing leaks between them by default.
Ask every workspace at once.
Choose the workspaces you belong to and ask. Only those are searched, each answer says where it came from, and a save lands in one.
askWhat did we decide about refunds?
searched, nothing relevant: Content
not searched: Product, Northwind · their answers never leave them
example data · search spans memberships, ownership stays put
A new customer gets its own workspace.
Northwind signs on Monday. By the afternoon they have a workspace, your proven workflows and their own people, walled off from yours.
A new customer signs.
Northwind is coming on board. One line in your AI client creates their workspace. It starts empty, with its own walls.
from the catalog, into northwind
- Taskuniversalinstall
- Planuniversalinstall
- Decision Memouniversalinstall
- Meeting Follow-Upsalesinstall
northwind owns its copies · edit them without touching yours
- YYouowner
- SSam, account leadadmin
- lead@northwind.examplememberpending
support reaches for northwind · nothing returned
Your best workflows come along.
Install the templates your team already trusts. Northwind gets its own copy, routed to its own work, editable without touching yours.
from the catalog, into northwind
- Taskuniversalinstall
- Planuniversalinstall
- Decision Memouniversalinstall
- Meeting Follow-Upsalesinstall
northwind owns its copies · edit them without touching yours
- YYouowner
- SSam, account leadadmin
- lead@northwind.examplememberpending
support reaches for northwind · nothing returned
Their lead joins with a role.
Invite by email as owner, admin or member. The invite waits for them to accept, and expires after seven days.
from the catalog, into northwind
- Taskuniversalinstall
- Planuniversalinstall
- Decision Memouniversalinstall
- Meeting Follow-Upsalesinstall
northwind owns its copies · edit them without touching yours
- YYouowner
- SSam, account leadadmin
- lead@northwind.examplememberpending
support reaches for northwind · nothing returned
The work runs inside the walls.
Northwind's tasks, approvals and memory stay in Northwind. Your support team never sees them. Their lead never sees yours.
from the catalog, into northwind
- Taskuniversalinstall
- Planuniversalinstall
- Decision Memouniversalinstall
- Meeting Follow-Upsalesinstall
northwind owns its copies · edit them without touching yours
- YYouowner
- SSam, account leadadmin
- lead@northwind.examplememberpending
support reaches for northwind · nothing returned
You still see the whole picture.
Ask one question and the search spans every workspace you belong to. Each answer says where it came from.
from the catalog, into northwind
- Taskuniversalinstall
- Planuniversalinstall
- Decision Memouniversalinstall
- Meeting Follow-Upsalesinstall
northwind owns its copies · edit them without touching yours
- YYouowner
- SSam, account leadadmin
- lead@northwind.examplememberpending
support reaches for northwind · nothing returned
from the catalog, into northwind
- Taskuniversalinstall
- Planuniversalinstall
- Decision Memouniversalinstall
- Meeting Follow-Upsalesinstall
northwind owns its copies · edit them without touching yours
- YYouowner
- SSam, account leadadmin
- lead@northwind.examplememberpending
support reaches for northwind · nothing returned
Separate by default. Searched together.
One per system
A team, a customer or an automated system. Each owns its tasks, workflows, policies, executors, settings and shared memory.
self-serve to create
Walled by default
Isolation is enforced in the database. A request with no workspace reads nothing. Nothing leaks unless you belong.
row-level security
Three plain roles
Owner, admin, member. Invites wait to be accepted and expire after seven days. No maze of permissions.
per workspace
Searched together
One question searches every workspace you belong to. Each answer is badged. Every write lands in exactly one.
one search, never one pool
One shared mess, or one per system.
- A customer's work sits next to your internal notes.
- One set of workflows bent to fit every team.
- Search returns everyone's noise.
- A new system means a new tool.
- A customer gets a workspace, walled off in the database.
- Each workspace installs the workflows it needs.
- Search spans only what you belong to, each answer badged.
- A new system is a new workspace.
Search spans memberships
Recall takes no workspace. It fans out across every verified membership in one query, and each result carries the workspace it came from.
{
"context_query": "refund approvals",
"returns": [
{ "workspace": "support",
"memory": "Over 200 needs a lead" },
{ "workspace": "finance",
"memory": "Post to month of sale" }
]
}Writes name exactly one
Every write resolves to one workspace. For someone in several, the workspace is required and a write without it is refused.
{
"memory_store": {
"workspace": "finance",
"category": "decision",
"content": "Refunds post to the
month of the original sale"
}
}Isolation lives in the database
Postgres row-level security with FORCE: even the table owner cannot step around it. App scoping and tenant middleware sit on top, not instead.
USING (
org_id = current_setting(
'app.current_tenant_id', TRUE)
OR org_id IS NULL
)Three roles, a real invite lifecycle
Owner, admin, member, checked at the route and service layer, and the last owner cannot be removed. Invites move pending to accepted, revoked, declined or expired.
{
"workspaces_members_manage": {
"action": "create",
"workspace": "northwind",
"email": "lead@northwind.example",
"role": "member"
}
}Workspace questions, answered.
What is a ConvOps workspace?
A ConvOps workspace is one walled operating space for a team, a customer or an automated system. It owns its own tasks, workflows, policies, executors, settings and memory, isolated in the database. Example: an agency runs one workspace per client, so each client's work, rules and history stay apart, while the agency staff search across the ones they belong to.
How many workspaces should I run?
In ConvOps, one per system you run is the pattern that holds up: a business unit, a client, a content pipeline, an automated operations loop. The boundary follows the system, not the org chart, because workflows, executors, policies and memory all live at the workspace level. Example: a clinic group runs one workspace per clinic and one for shared services.
Is memory shared between workspaces?
Search is unified; ownership is not. In ConvOps one recall fans out across every workspace you belong to, but each memory stays owned by its workspace and isolated at the database layer, and writes always resolve to exactly one workspace. Example: during an acquisition, a clean team works in its own workspace that the wider company cannot read.
Who can see what?
ConvOps members see the workspaces they belong to, under three plain roles: owner, admin and member. Invites follow a real lifecycle with expiry after seven days, revocation and decline, and isolation is enforced by row-level security the table owner cannot bypass.
Can different workspaces execute on different infrastructure?
Yes. ConvOps sets execution per workspace: one system can run on ConvOps cloud while another dispatches to your own OpenCode server or your own runner, without any task definition changing. Example: a regulated business unit keeps its runs on its own runner while marketing runs in the cloud.
What does creating one involve?
Creating a ConvOps workspace is self-serve: name it and it exists, with its own settings catalog ready to tune. You can install the workflow templates your team already trusts, and the new workspace gets its own copy. A new automated system starts with a workspace, not a procurement cycle.