> 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/getting-started/the-partner-workspace-1.md). # The Partner workspace Everything a partner does lives behind five groups in the navigation rail on the left. The order is deliberate: the things you look at daily are at the top, and the things you configure once are at the bottom. ## The five groups ### Overview | Screen | What it is for | | ------------- | ----------------------------------------------------------------------------------------- | | **Dashboard** | Your firm's headline figures, and the setup checklist while you are still getting started | | **Radar** | Everything the automated agents have noticed and nobody has dealt with yet | ### Clients | Screen | What it is for | | ----------------------- | ------------------------------------------------------------------------------------------ | | **Clients & contracts** | Every client, their lifecycle stage, and their commercial contracts | | **Pipeline** | Job requisitions, candidates, offers, and the hire that turns a candidate into a placement | | **Client sign-offs** | Timesheets waiting on a client's approval, and the ones that have gone stale | ### People | Screen | What it is for | | ------------- | --------------------------------------------------------------------------- | | **Roster** | Every consultant, their agreement, credentials, documents and custom fields | | **Org chart** | Who reports to whom | | **Wellbeing** | Pulse check-in results and the consultants whose trend is deteriorating | ### Time & money | Screen | What it is for | | ------------- | ------------------------------------------------------------------------------------ | | **Team time** | Timesheets across the whole team, week by week | | **Invoicing** | Generating, sending and tracking invoices, and recording payment | | **Expenses** | Expenses submitted against engagements | | **Payroll** | Payroll runs, provider assignment, and the export files | | **Margin** | What each engagement earns against what it costs | | **Reports** | Revenue projection, AR aging and DSO, utilization, and the engagement lifecycle view | ### Configure | Screen | What it is for | | ---------------------- | --------------------------------------------------------------------------------------------- | | **Agents** | The automated sweeps: what each one watches, how often it runs, and what it may do unattended | | **Document templates** | The wording used to generate MSAs, SOWs, NDAs and offer letters | | **Settings** | Your firm's own configuration — branding, payment rail, rate card and the rest | > **Document templates and Checklists are different things.** *Document templates* (Configure) are the contract and offer-letter wording. *Checklists* (Settings) are the onboarding and offboarding task lists. They are named apart on purpose. ## Finding your way **Groups collapse.** Click a group heading to fold it away. The workspace remembers which groups you collapsed, per area, so the rail stays the shape you left it. **Breadcrumbs show depth.** On detail screens the top bar shows the trail that got you there — for example a candidate sits under a job requisition, which sits under Pipeline. Breadcrumbs are derived from where you actually are, so they are never stale. **On a phone, the rail becomes a drawer.** At narrow widths the rail is replaced by a menu button in the top bar; tapping it slides the same navigation in from the side. Every screen is usable down to small phone widths — nothing is desktop-only. ## Example data If your workspace was seeded with example data so you could try things out, you will see: * a **banner** across the top of the workspace saying so, and * a **sample** chip on every seeded record. Example data behaves like real data everywhere except that the automated agents ignore it — a seeded client will never produce a finding on Radar, and a seeded consultant will never be chased for a timesheet. That is what keeps a demonstration workspace from filling your real work queue. An admin can remove it all from **Settings → Example data** when you are ready to work for real. See [First-day setup](/getting-started/first-day-setup-1.md). --- # 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/getting-started/the-partner-workspace-1.md?ask=&goal= ``` `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.