Member governance & approvals
Member governance is an optional, per-organization control. When it’s on, anything a member creates is held as pending approval and can’t be used until an owner or admin approves it. It’s off by default — turning it on changes nothing retroactively, it only gates new member-created resources.
What gets held for approval
Section titled “What gets held for approval”With governance on, these — when created by a member — land in pending approval:
- Agents
- Integrations (connections)
- Knowledge
- Flows
- Skills
- Voices
A pending resource is inert: a pending agent can’t be run, a pending connection can’t be used by an agent, and so on — until it’s approved. Owners and admins create things already approved.
Turning it on
Section titled “Turning it on”- Go to Settings → Organization
- Toggle Member governance on
Only the owner can change this setting.
Approving items
Section titled “Approving items”Owners and admins get an Approvals inbox in the sidebar (with a count badge):
- Open Approvals
- Review each pending item
- Approve to make it live, or Reject with an optional note
Approvals are recorded in the organization’s activity log.
When to use it
Section titled “When to use it”Turn governance on when you want members to draft agents, connections and knowledge, but want an owner or admin to sign off before anything goes live — useful for regulated teams, shared production orgs, or onboarding new members.
See also: Organization governance · Roles & permissions · Agent access.

