> For the complete documentation index, see [llms.txt](https://help.agencydesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.agencydesk.io/jobs/central.md). # Central The Central tab is a Job's shared record: every Task Note, every action taken, every meeting, and every document attached anywhere on the Job, in one view. **Central** is the Job's shared record. Notes written on individual [Tasks](/jobs/tasks.md), the full history of what has been done on the Job, meetings scheduled against it, and every document attached anywhere on it all surface here. Because Agencydesk was built exclusively for agencies, this material is collected rather than filed. The brief attachment sits with the supplier quote and the client's feedback note, so an Account Executive picking up a Job halfway through has one place to read rather than four to search. The tab is split in two. The left side carries **Task Notes** and **Activity**, the right side carries **Meetings** and **Job Documents**. Each panel has its own **Search**. ## Task Notes The **Task Notes** view collects every [Note](/jobs/tasks.md#notes-tab) written on any Task in the Job. Each entry shows the author's profile picture, a line reading who commented and on which Task, and a timestamp. The Task name is a link, so you can jump straight to it. Any user tagged with **@** appears as a highlighted mention in the body. Click **Reply** on a Note to respond without leaving Central. {% hint style="info" %} **Great for** a Monday catch-up on a busy retainer. Read every conversation happening across a dozen Tasks in one scroll, reply where you are the blocker, and click through only where the Task itself needs opening. {% endhint %} ### Adding a Job Note Click **+ Add a Note** to write a Note against the **Job** rather than a Task. A Job Note only ever appears here in Central. It has no Task to attach to, so it does not show a speech bubble on the Tasks list or open anywhere else. This is the right place for something that concerns the whole Job rather than one piece of it: a change in client contact, a note that the budget has been signed off verbally, or context the next person on the Job will need. ## Activity The **Activity** view is the Job's audit trail, newest first. Each line records who did what, when, and to what value. It captures actions across the whole Job, including: * [Cost Estimates](/jobs/estimates.md) created and activated, with the CE number and total * [Invoices](/jobs/financial/invoices.md) created and issued, with the Invoice number and total * [Job Brief](/jobs/managing-jobs.md#the-job-brief) updates {% hint style="info" %} **Great for** answering the question nobody can ever remember the answer to. Which Estimate was approved, who issued the Invoice, when the brief last changed. The Activity feed reconstructs it with names and timestamps instead of anyone trawling through email. {% endhint %} ## Meetings The **Meetings** panel lists meetings scheduled against this Job, each showing its title, the date, the start and end time with the duration, and the number of attendees. When there are none, the panel reads *No meetings scheduled*. Click **+ Schedule a Meeting** to add one. {% hint style="info" %} Meetings also appear on the attendees' [My Desk](/my-desk/my-desk.md) and in the [Calendar](/calendar/calendar.md), and sync with Google Calendar or Microsoft 365 where that [Integration](/company-settings/integrations.md) is connected. {% endhint %} {% hint style="info" %} **Great for** keeping client meetings attached to the work they concern. A status call booked against the Job sits alongside the notes and documents from that conversation, rather than living only in somebody's calendar. {% endhint %} ## Job Documents The **Job Documents** panel gathers every file attached anywhere on the Job. Documents are grouped by where they came from. Files attached to the Job itself sit at the top, then files attached to a Task or a Cost appear beneath that item's name. Each file shows a thumbnail, its name, the date and time it was added, and its size, with icons to **delete**, **preview**, or **download** it. ### Where documents come from Files reach Central from four places, and all of them collect here automatically: * [**Task Briefs**](/jobs/tasks.md#brief-tab) — grouped under the Task name. * [**Task Amendments**](/jobs/tasks.md#adding-an-amendment) — grouped under the Task name. * [**Costs**](/jobs/costs.md#documents) — grouped under the Cost name. * The [**Job Brief**](/jobs/managing-jobs.md#the-job-brief) — listed as Job documents. ### Uploading directly Drop files into the **Drop documents or select files** area at the bottom of the panel, or click to browse. A file uploaded here attaches to the **Job** rather than to any Task or Cost, so it lists as a Job document and also appears on the [Job Brief](/jobs/managing-jobs.md#the-job-brief). The two are the same set of files viewed from two places, so it makes no difference which end you upload from. {% hint style="info" %} **Great for** an audit or a client handover. Every signed approval, supplier quote, brand guideline, and reference file the Job touched is in one list, grouped by the work it belongs to, without anyone assembling it after the fact. {% endhint %} --- # 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://help.agencydesk.io/jobs/central.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.