> 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/welcome-to-allshore.md).

# Welcome to Allshore

Allshore is the operations back office for **vertical partner firms** — independent recruiting and consulting firms that run their whole engagement lifecycle on one platform: job requisition → candidate pipeline → placement → timesheets and client approvals → invoicing → payroll exports → margin.

## Who this guide is for

This guide is written for **partner teams** — the people who work at a vertical partner firm. In Allshore, your firm is a *tenant*: everything you see and everything you create belongs to your firm alone. Your staff hold one of two roles:

| Role              | What it means                                                                                                                                                                         |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Partner admin** | Full access, including money-final actions (approve/execute payroll, void invoices), sensitive reveals (payout details), credential verification, agent approvals, and configuration. |
| **Partner user**  | Day-to-day operations: clients, pipeline, roster, time, invoicing prep, reports.                                                                                                      |

Admin-only controls are always **visible but disabled** for partner users — if you can see a button you can't press, that's your cue to ask an admin, not a bug.

Consultants and your clients' contacts have their own, much smaller areas (the consultant workspace and the client portal). This guide covers them from *your* perspective: what you manage, and what they see.

## How the Partner workspace is organized

The navigation rail groups everything into five sections — the same order this guide follows:

| Nav group        | Screens                                                  |
| ---------------- | -------------------------------------------------------- |
| **Overview**     | Dashboard, Radar                                         |
| **Clients**      | Clients & contracts, Pipeline, Client sign-offs          |
| **People**       | Roster, Org chart, Wellbeing                             |
| **Time & money** | Team time, Invoicing, Expenses, Payroll, Margin, Reports |
| **Configure**    | Agents, Document templates, Settings                     |

## Three boundaries to know from day one

1. **Allshore never holds funds or files taxes.** It computes, exports, and records — money moves on your own rails (bank, payroll provider, Stripe).
2. **Your clients never see pay rates, classifications, margins, other clients, or wellbeing data.** The client portal is hard-fenced to executed contracts, approvals, invoices, and compliance *status* only.
3. **No e-signature and no sourcing.** Allshore generates and tracks documents (MSA/SOW/NDA, offer letters) but signing happens outside; countersigned PDFs are uploaded back. There are no job-board integrations or resume parsing.

## The guide

* [Getting started](/getting-started.md) — signing in, finding your way around, first-day setup.
* [Clients & pipeline](/clients-and-pipeline.md) — clients, contracts, documents, pre-sale, recruiting, sign-offs.
* [Your team](/your-team.md) — roster, compensation, onboarding, time off, credentials, wellbeing.
* [Time & money](/time-and-money.md) — timesheets, invoicing, payroll, margin, reports.
* [Automation & Ally](/automation-and-ally.md) — Radar, agents, the MCP connector, and Ally in Slack.
* [Your clients' portal & trust](/your-clients-portal-and-trust.md) — what clients see, and how your data is protected.


---

# 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/welcome-to-allshore.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.