> 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

Read Job and Task conversations in Central, search Mentions me, reply and add notes, and find Activity, meetings and shared documents.

**Central** is the Job's shared record. Notes written on individual [Tasks](/jobs/tasks.md), recorded activity 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 left panel has **Notes** and **Activity** tabs; the right panels have **Meetings** and **Documents**. Each area has Search. Notes collects Task conversations as well as Job-level notes.

## Notes

The **Task Notes** view collects every [Note](/jobs/tasks.md#notes-tab) written on any Task in the Job.

Each thread shows the author, timestamp and Task link where it belongs to a Task. User tags appear as highlighted mentions. Replies stay beneath the original note, so the full conversation can be read together.

{% stepper %}
{% step %}
Click **Reply** beneath the note you want to answer.
{% endstep %}

{% step %}
Write your response. Use **@** and choose a user when their attention is needed.
{% endstep %}

{% step %}
Click **Reply** to save the response, or **Cancel** to close it.
{% endstep %}
{% endstepper %}

### Finding conversations that mention you

{% stepper %}
{% step %}
Open **Notes** in Central and click **Mentions me**.
{% endstep %}

{% step %}
Read the matching threads. A mention in either the original note or any reply brings the whole conversation into the result.
{% endstep %}

{% step %}
Use Search to narrow those threads by note/reply text, author or Task.
{% endstep %}

{% step %}
Click **Mentions me** again to return to all notes. Clear Search as well if you want the complete list.
{% endstep %}
{% endstepper %}

The number beside **Mentions me** counts conversations containing a mention of you. It is not an unread count or a checklist of acknowledgements. The count covers all matching conversations even when Search narrows what you can see.

Mentioned threads are lightly highlighted in the normal view too. While Mentions me is selected, the new-note composer is hidden; turn the filter off to write a Job note. An in-progress composer is kept while filtering.

{% hint style="info" %}
A designer is mentioned in a reply halfway through a client-feedback thread. Mentions me brings up the whole exchange, so they can read the instruction in context and reply without searching every Task.
{% endhint %}

{% 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

{% stepper %}
{% step %}
Open **Notes** in Central. Turn off **Mentions me** if the composer is hidden.
{% endstep %}

{% step %}
Click **Write a note…** and write the Job-level update. Use the compact toolbar for formatting, lists and links; type **@** to select a user.
{% endstep %}

{% step %}
Click **Add note** to save it. Use **Cancel** if you do not want to add it.
{% endstep %}
{% endstepper %}

For a saved note or reply you wrote, hover to reveal **Edit** and **Delete**. Save an edit with **Save**; deleting asks for confirmation. Closed Jobs keep the conversation read-only.

{% hint style="info" %}
Type the message in the editor, then use its action button to submit. Enter in the editor is for a new line. Central waits for an inline image upload to finish before allowing the note to be saved.
{% endhint %}

Task-level notes are written from the Task’s [Notes tab](/jobs/tasks.md) and appear in the same Central conversation view.

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 shows the Job’s recorded activity, newest first. Entries show the type and date/time above the person or System and the action, with an amount where one is recorded.

Recorded entries can include:

* [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" %}
An account executive checking which quote was activated or who issued an Invoice can review the recorded events here. Use **Search** to narrow this wider Job timeline. Financial and Estimates also show their matching document entries behind a closed Activity heading. Missing activity does not prove that an action never happened.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.agencydesk.io/jobs/central.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.