> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getoneprofile.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Assistant

> Set the credit threshold above which the AI Assistant asks first, and choose what it may change in your workspace without asking.

One rule decides whether the AI Assistant asks before changing your workspace or goes ahead. It is made of your spend threshold and the short list of changes you allow without asking, both under **Approvals** on this page.

## Set the spend threshold

On [AI Assistant](https://app.getoneprofile.ai/settings/ai-assistant), the line **Ask before spending** holds a number in whole credits, followed by **credits or more**. Type a new number and press Enter, or click away, to save it.

Any change priced at or above that number always waits for your **Approve**, whatever else you allow. Free work never counts as a spend. The same number sets when a column run on a table asks you to confirm before it starts.

## Allow changes without asking

Under **Allowed without asking**, each row is one kind of change with a switch. A change that is on applies as soon as the assistant proposes it, with **Undo** on its card. Everything else arrives as a proposal and waits for **Approve** or **Dismiss**.

Every new conversation starts with this list. In a conversation, **Approve and allow in this conversation** on a card adds that kind of change for the rest of the conversation only.

## Good to know

<AccordionGroup>
  <Accordion title="Which changes can never be allowed without asking?">
    Anything that reaches someone outside the workspace. Pushing rows to a connected tool reads **Always asks**, and adding contacts to a sequence reads **Asks when the sequence is running**: allowed, it still asks whenever the sequence is live.
  </Accordion>

  <Accordion title="Does Undo give the credits back?">
    No. **Undo** reverses the change in your workspace, such as removing the column that was added. A spend that already happened stays on your usage, and the card says so.
  </Accordion>

  <Accordion title="Why does the table ask me to confirm a run at this number?">
    The confirmation before an expensive column run uses the same threshold, so one number decides when a person is asked, whether the assistant or you started the work.
  </Accordion>

  <Accordion title="Can an agent get its own list?">
    Yes. An agent's editor has a **Workspace actions** section with the same switches, starting from this page's defaults. **Use workspace defaults** hands the list back, so a change here reaches every agent that never set its own.
  </Accordion>

  <Accordion title="Who can change these settings?">
    Anyone in the workspace. A change reaches every conversation and agent that follows the defaults straight away.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Chat" icon="message-square" href="/assistant/chat">
    Ask for a change and watch it arrive as a card.
  </Card>

  <Card title="Run columns" icon="play" href="/tables/run-columns">
    How a run is priced, held and confirmed before it starts.
  </Card>
</CardGroup>