---
title: "Questions and approvals"
description: "When SourceGeek asks you a question or asks before it acts in another tool, and how admins choose how often it asks."
---

> Documentation Index
> Fetch the complete documentation index at: https://support.sourcegeek.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Questions and approvals

## Questions

When SourceGeek needs more information, it asks with a **Questions for you** card. Pick an answer, choose **Other…** to write your own, and click **Submit**. You can also just reply in the chat.

## Approvals

Before SourceGeek does something that changes data or reaches people outside SourceGeek, it shows an **Approval required** card with what it wants to do. For example:

- Sending an email or a message, or creating a draft, through a connected tool
- Creating, updating or moving a record in your ATS or CRM
- Creating, scheduling or changing an event
- Starting tasks in a [project](/projects) or setting a task to repeat
- Creating, pausing or resuming an [automation](/automations)
- Forgetting a [memory](/memory) or deleting [company context](/memory#company-context)

Choose:

- **Approve**: do it this once
- **Approve for this chat**: do it, and don't ask again for this tool in this chat
- **Decline**: don't do it
- **Reply instead…**: decline and tell SourceGeek what to do differently

Reading data, such as searching your inbox or looking up a candidate in your ATS, doesn't ask for approval.

## Who can answer

Only the person whose message led to the question or approval can answer it. In a [shared chat](/chats#shared-chats), others see that it's waiting. That's also why SourceGeek only ever uses your own connectors for your messages.

## How often SourceGeek asks

A workspace admin sets this under **Settings → General → Agent approvals**, "Approval for emails and other external actions":

- **Ask every time**
- **Ask once per chat** (the default): after you approve a tool once in a chat, SourceGeek uses it again in that chat without asking
- **Never ask (auto-approve)**

With **Ask once per chat**, a few actions still ask every time, because one approval could cover more than you saw: changes on WordPress.com and payroll in Gusto.

[Automations](/automations) run unattended, so scheduled runs and **Run now** don't ask for approval. Runs started by a webhook do, because their input comes from outside SourceGeek.

## See what SourceGeek did

Everything SourceGeek changed through a connector is listed under **Settings → Usage → Agent activity**: what it did, whether it was approved, completed, declined or failed, and a link back to the chat. For changes in an ATS there is often a link to the record and a tip on how to undo it.

Source: https://support.sourcegeek.com/approvals/index.mdx