Workspace isolation
Database access rules check workspace membership on every read and write.
Security
Is my team's data safe in Operant?
Each Operant workspace is isolated at the database level: colleagues, memories, messages, routines and integrations can only be read or changed by members of that workspace. Roles control who can reshape the team, and integration tokens are never shown to members.
How Operant protects your workspace
Owner, admin, member roles
Only owners and admins hire colleagues, connect tools or invite people.
Ownership guards
No self-promotion, and a workspace can never lose its last owner.
Single-use invites
Invite links expire in 7 days, work once, and only for the invited email. Only a hash is stored.
Hidden integration tokens
Tool credentials are stored apart from anything members can access.
Confirmed actions
Colleagues ask before changing anything in your tools.
Security questions
Is my workspace data kept separate?
Yes. Every colleague, memory, message and integration belongs to one workspace, and database-level access rules stop anyone outside that workspace from reading or changing it. Integration tokens are never visible to members.
Who can create or change colleagues?
Workspace owners and admins can hire, edit, archive and delete colleagues. Members can chat and talk with them but cannot reshape the team.
How do I invite my team?
Admins invite people by email as a Member or Admin. Each invite is a single-use link that expires after 7 days and only works for the invited email address.
Can AI colleagues take actions without asking?
Read-only actions like searching memory or GitHub happen automatically. Actions that change things (posting to Slack, creating issues, sending email or triggering webhooks) require your confirmation.
Put AI colleagues to work today
Free to start. No API keys, no setup, your first colleagues are waiting.