All solutions
Support function · IT and security

One workspace for the organisation, with roles that say who uses an agent and who changes it.

Agents appear across the company with no single place to see who uses and who changes them.

For IT, security and the teams that answer to auditors, across every department.

How the example fits together: tools and an agent built on Unflood, with a person approving before anything is written.

Made from a conversation in Claude, released to the AI platforms your team already uses, running in your own environment.

Claude
Turn this conversation into an agent for the whole company, and let only the IT team change it.
Unflood created the agent from this conversation, ran its tests and released it under the production policy.
  • Unflood: Agent created from this conversation 3m ago
  • Unflood: Tests run on the new agent 2m ago
  • Unflood: Held to the production release policy 1m ago
  • Unflood: Staff can use it, only the IT team can change it Just now

See it happen in a chat

A person on the team asks for an agent. Unflood does the building in the background and comes back for the decisions that are yours.

  • Unflood tests them.
  • A person approves each release.
  • They are shared with the right people.
  • They are kept up to date, so you step in only when a decision is yours.

Examples for IT and security, to learn from

Example 1

Keep one workspace for the organisation, on its own domains

On Unflood: A workspace on the organisation's own domains.

Example 2

Give each person a role: who uses an agent and who changes it

How governance fits together

Workspace
One for the organisationOn its own domains.
Members
A role for each personWho uses an agent and who changes it.
Policy
One release policySets how an agent may be released.
Person
The IT admin owns itOne owner for the whole workspace.

Six moments that make the difference

Each one is shown on sample data, with this team's own example where there is one.

Build it from a conversation

Describe the agent in a Claude chat. Unflood records it, its tools and its tests.

In IT and security: Keep one workspace for the organisation, on its own domains

Recorded from the conversation
WorkspaceRolesPolicyIT admin
Drawn on sample data.

Test it

Suites and a judge run it; each failed case becomes an item to fix.

Test lab
  • A case failsJudged against the version tested.
  • It becomes an item to fixNothing is lost between runs.
  • Retest, then release
Drawn on sample data.

Release it with approval

Package a version. Nothing reaches people without a person's approval; the builder cannot approve their own.

  • Release policyProduction takes only releases that passed the suite and came from staging.
Release waiting for approval
  • Packaged by
  • Needs approval from
The builder cannot approve their own release.
Drawn on sample data.

Share it

Choose who can use it, person by person or team by team, where the team already works.

In IT and security: Every team lead.

  • Uses itEvery team lead.
Who can use it
  • The IT and security teamEvery team lead.
  • A named personChoose person by person or team by team.
Drawn on sample data.

Keep it up to date

Change it, retest it, release the next version. Every version can be rolled back.

Versions
  • Current versionLive.
  • Next versionChanged, retested, waiting for approval.
  • Roll backEvery version can be rolled back.
Drawn on sample data.

The organisation stays in control

Members, roles and a record of every change belong to the organisation.

  • WorkspaceOne per organisation, on its proven domains.
  • Members and rolesWho uses an agent and who changes it.
  • A workspace for the organisation, on its proven domains
  • Members and roles: who uses an agent and who changes it
  • Release approval by a second person
Record of every change
  • IT adminProves the company's domains.
  • IT adminSets one policy for venues, models, spend and retention.
  • UnfloodReads one register: every agent, its owner and each host's live version.
Drawn on sample data.

How the team gets there faster

Your people describe the work and approve it. Unflood does the building, testing and publishing.

Today

Agents appear across the company with no single place to see who uses and who changes them.

With Unflood

One workspace for the organisation, with roles that say who uses an agent and who changes it.

Your people do
  • Owns itThe IT admin.
  • Sets release policyThe head of security.
  • Uses itEvery team lead.
Unflood does
  • Connects your tools and data
  • Writes and runs the tests
  • Packages each version
  • Publishes it where your team works
  • Retests every change before the next release
  • Keeps the record of who changed what

In the reference journey's recorded replay: 3 steps, 1 by Unflood and 2 by your people. Counted from the journey fixture, on example data.

Talk to us about your team

Tell us the work your team wants an agent for. We set up a workspace with you and build the first one with the people who know the work.

Get in touch