Skip to main content
Octolane maintains your CRM automatically and brings decisions to your team when review is needed. Approval behavior depends on the action and workspace configuration; not every record update requires a separate click.

Review a proposed action

  • Approve: allow the proposed action.
  • Edit: correct the proposal before approving it.
  • Reject: decline the action and provide context when useful.
Review the target record, recipients, and proposed change. Your approvals and edits help Octolane learn how your team works. New company-brain learnings wait for review before they are retained.

Configure automatic work

Use workspace agent and approval settings to choose which actions require review and which can run automatically. Routine record updates, enrichment, and configured sequences or automations follow those settings and your plan’s limits. Follow-up drafts can be reviewed before sending. An authorized sequence or automation can send on its configured schedule, so an individual approval is not required for every message in every workflow.

External agents and API calls

MCP and REST requests act with the connected member’s permissions. A write tool or API request can apply a change directly. The in-app approval queue is not a universal review layer for integrations. Configure the external client’s confirmations and keep requests within the user’s authorization. Read the target record before an update and verify the result afterward. See Octolane for AI agents.