The agent your IT team can sign off.

Arqivon for Teams puts the personal agent in a shared workspace with roles, single sign-on, provisioning, data residency and an audit trail. Approval gates fail closed.

Talk to us about Teams See the controls

Rolling out. Teams is not generally available yet.

Harbour Studioexample workspace · us-central1
AnaownerSSO
SamadminSSO
PriyamemberSCIM
Sign-in
SAML · OIDC
Provisioning
SCIM
Connectors
gmail · calendar
Retention
set per workspace

→ Priya's agent drafted an email · approval required

→ Priya approved · sent · audit event written

→ connector slack not on the allowlist · refused

Controls, in plain words.

  • Roles

    Every person is an owner, an admin or a member. Admins can see metadata for the members of their own workspace, never another workspace's.

    Each person's data stays under their own account. Admins manage the workspace, not people's inboxes.

  • Connector policy

    Choose which connectors the workspace may use: Gmail, Calendar, Telegram, WhatsApp, Slack and Discord. A connector that isn't on the list is refused.

  • Fail-closed approvals

    An approval that can't be checked is a no. Send, pay, delete and login always wait for a tap, and a workspace can't relax that.

  • Audit and export

    Approvals and actions write audit events. Admins can read the workspace audit and export member and job metadata.

    Exports leave out secrets and message bodies.

Sign-in that fits your identity provider.

Connect SAML or OIDC for single sign-on, and SCIM to provision and deprovision people from your directory. The workspace owner can't be deprovisioned by SCIM.

  • SAML assertions and OIDC code flow per workspace.
  • SCIM v2 Users: list, create, deactivate and delete.
  • Client secrets and certificates are stored apart from the workspace record.
# configure (workspace admin)
PUT    /api/org/sso
POST   /api/org/sso/scim-token

# sign-in
POST   /api/org/sso/acs            SAML
GET    /api/org/sso/oidc/start     OIDC

# provisioning (SCIM v2, bearer token)
GET    /api/scim/v2/Users
POST   /api/scim/v2/Users
PATCH  /api/scim/v2/Users/{id}
DELETE /api/scim/v2/Users/{id}

Your data stays where you put it.

Residency, retention and erasure are workspace settings, not a support ticket.

  • Data residency

    A workspace has a region. The service handling a request has to be in that region, and a region without a store can't be selected.

    Moving a workspace copies its jobs, audit and vault into the target region, then removes them from the source.

  • Retention

    Set how many days the workspace keeps completed work. Retention is part of the workspace policy.

  • Erasure

    Delete a person's workspace data: their jobs, pairing links and vault tokens. Erasing data does not delete their sign-in account.

Talk to us about Teams.

Teams is rolling out. Leave an email and we'll write when it opens to your kind of organization. There is no public price yet, and nothing is charged.

Or write to emmanuel.veranyuy@gmail.com.

Arqivon for Teams

Not a login and not a charge.