Skip to content
Leadbase

Approvals and safe Assistant actions

Choose the right approval mode and review proposed research or changes before they run.

The approval control in the Assistant composer applies to actions, not ordinary conversation. It does not change what the Assistant can read: it remains limited to the Sheets and workspace data you are already allowed to access.

Choose the right mode

ModeWhen the Assistant pauses
Ask for approvalBefore edits or research. Use this when you want to inspect every proposed action.
Approve for meOnly for sensitive actions. This is the default balance for routine work.
Full permissionIt runs actions without asking again. Use it only for a tightly scoped, reviewed task.

The preference is saved for your Assistant use. It is not a way to bypass workspace roles, Sheet sharing, billing controls, or another person’s access boundaries.

Review an action before you approve it

Read the target Sheet, rows, columns, intended operation, and any stated cost or external research step. Check that the request names the right dataset and that the result will be useful before you approve. If the action changes data, make sure the team knows whether the change is a test, a one-time correction, or a repeatable workflow.

Use Ask for approval for unfamiliar work, broad enrichment, and actions that could change many rows. Keep Full permission temporary: switch back once the scoped task is complete.

Treat output as a draft, not proof

Assistant text, research, and file summaries can be incomplete or wrong. Inspect source material and resulting cells before you rely on them externally. For product how-to questions, the Assistant can retrieve canonical Leadbase documentation; follow the linked guide when it gives a more precise workflow or permission boundary.

See Use the assistant for attaching context and Enrich data in a Sheet before you approve enrichment work.