Permissions

Permissions control which tools a virtual coworker can use when generating a response. The safest option is to allow only what is needed for the job.

Permission types

  • Read: Allows the coworker to read data in your workspace.
  • Write: Allows creating and modifying data.
  • Delete: Allows deleting data.

A coworker can still comment without any tools, but tools help them verify facts or add detail.

Autonomy and allowed actions

Use Autonomy to set the highest behavior level: Observe, Suggest, Draft, Requires approval, or Execute. Observe and Suggest only expose safe read tools. Draft additionally permits draft-only actions. Requires approval exposes allowed write actions through Bnder's approval flow. Execute permits allowed actions that the tool does not classify as sensitive; sensitive actions remain gated.

Allowed actions narrow the broad permissions for CRM and connected work. You can independently allow CRM reads, connected-data reads, task or Ticket creation, Record creation, field or status updates, Relationships, Commitments, integration calls, communication, and sensitive actions. A coworker needs both the applicable Read/Write permission and the action grant.

CRM context sent to a coworker contains workspace terminology, configured Record Types and fields, layouts, Relationships, and permission-visible activity. OAuth tokens, API keys, webhook secrets, payment credentials, and raw provider payloads are removed. Completed CRM actions appear in the CRM agent execution history with the action, affected entity, source freshness, approval status, outcome, and time; hidden reasoning is never shown or stored there.

Warning: 

Write and delete permissions can impact data across the workspace. Combine permissions with project scope to keep access appropriate for the coworker's role.

  • Reviewer only: Read
  • Assistant: Read + Write
  • Cleanup or compliance: Read + Write + Delete

If you are unsure, start with Read and expand permissions later.