> For the complete documentation index, see [llms.txt](https://wiki.roaddirect.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.roaddirect.co.nz/eboard/library/staff-documents.md).

# Staff documents

Staff documents are files stored against individual staff members, such as copies of qualifications, licences or signed forms.

To open it, go to **Library** → **Staff Documents** in the eBoard navigation bar. You can also open a staff member's documents from the [Users](/eboard/resources/users.md) page: click the **⋮** menu on their row and choose **Staff documents**.

## Browsing documents

Each staff member has a tab at the top of the page. Click a name to see that person's documents, with their **Type**, **File Name**, **Description**, **Expiry Date** and the date they were **Added to Library**.

## Add a document

1. Click **Add Item to Library**.
2. Choose the **Staff** member the document belongs to.
3. Enter a **Description**.
4. Enter an **Expiry** date if the document expires (for example a first aid certificate).
5. Under **File name**, drop the file in, paste it, or click **Select from Device**.
6. Click **Save**.

The user menu (your name, top right) also has a **My Documents** link.


---

# 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://wiki.roaddirect.co.nz/eboard/library/staff-documents.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.