Ask your Sidekick, then decide.

Prepare the workspace

Check the active company, your access to the source records and available AI allowance. A file or conversation link does not grant access to its underlying records.

Example: North Studio

Maya asks: “For Willow Bakery’s Website refresh, list open tasks and unpaid invoices. Use the latest client conversation. Do not make changes yet.” She then checks the actual tasks and invoice before requesting a proposal.

Ask about a record, not about the business in general

1. Open Sidekick in the sidebar. On a phone, use Sidekick in the bottom navigation.
2. Ask something you could also look up, such as "What tasks are still open for me?" Name the client, project or date when that narrows it.
3. Answer any clarification form it shows. Then open the underlying task, invoice or thread before you rely on the reply.

Approve the change, or reject it

When your Sidekick proposes a change, use Approve or Reject. If several proposals appear together, Approve all and Reject all are available. Read the set before you use either one.

A skill can hold a standing instruction, such as how you name projects. Add it in Settings → AI with New skill, write what it is for, and leave it enabled only if you want it used. A skill does not widen your permissions. Interactive proposals still use the approval controls; separately configured background automation can act without an approval for each change.

Stay in the company you mean

Answers use the active company's records and the access your role already has. Switch company before you ask about the other workspace. A company switch reloads that workspace.

AI use is metered against the company allowance. If your role can open Settings → AI usage, that is where consumption is listed. Plan allowances are on Plans & pricing.

Treat a drafted email as a draft. Check recipients, amounts and dates before Send. Sending still goes through the mailbox you chose.

Check the outcome

Read the proposed action’s target and values before approval. Afterwards, open the affected record and verify the result. For a long email analysis, inspect its background status rather than submitting the same request repeatedly.

Avoid a common mistake

Interactive proposals and separately configured background automation behave differently. Background analysis or automation can create or update records without an approval card for every action. A skill is an instruction, not a permission grant.