> For the complete documentation index, see [llms.txt](https://docs.allshore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allshore.ai/automation-and-ally.md).

# Automation & Ally

Allshore watches your operation continuously and does routine work for you — always inside your firm's fence, and always with a human gate on anything that leaves the building.

## Radar

**Radar** (Overview group) is the triage inbox for what the platform noticed: missing timesheets, paperwork gaps, expiring contracts and credentials, invoice anomalies, budget burn, margin drift, bench risk. Findings carry severity, deep links, and first/last-seen dates; **resolve** or **dismiss** them, and a finding that recurs after being resolved reopens rather than duplicating. Repeated sweeps never pile up copies — the same condition stays one finding.

## Agents

Scheduled **agents** (Configure group) run your recurring workflows: timesheet chasing, month-end invoice assembly, collections follow-up, paperwork sentinel, credential expiry watch, contract renewal watch, budget burn projection, margin drift, bench radar, onboarding chase, wellbeing sentinel. Each has a configurable cadence and a bounded tool scope.

The **approval gate** is the key concept: an agent that wants an *external* effect (anything a client or consultant would see — an email, a drafted document) queues an **approval task** for a human instead of acting. You approve or reject from the Agents screen; approved actions execute with **your name attributed**, and unactioned tasks expire after 3 days. Internal effects (a nudge to a consultant, a finding on Radar) run automatically.

## The MCP connector

Your whole workspace is also available conversationally: connect Claude (or any MCP client) to Allshore's connector and ask real questions — "what's outstanding on Northwind?", "who's unbilled this month?". The catalog is filtered to your role, every call is fenced exactly like the web app, and send/destroy-class tools require an explicit confirmation. What you can't do in the app, you can't do through the connector.

## Ally in Slack

**Ally** brings the same assistant into Slack: link your Slack identity to your Allshore account (Settings → Slack), and Ally answers as *you* — it can only see and do what you can, every action is audited under your name, and sends require an in-chat confirmation. Unlink at any time to revoke access instantly. *(Ally is rolling out — the account-linking and conversation foundation is live; the conversational loop is in active development.)*

*Detailed pages per area are being added — tracked in Linear milestone **M30**.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.allshore.ai/automation-and-ally.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.