> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/staff-files-an-overview.md).
# Staff Files
With Staff Files you can add documents to an online repository within flaik that all of your staff can access - either on their phone or via a desktop browser.
There is a 5MB limit per file. There is currently no cap on the total number of files that you can add or the total storage per resort.
Video and step-by-step instructions below.
### Video overview
{% embed url="" %}
### Step-by-step
Using Staff Files is simple! You just need to set up categories and upload files. However, you'll want to make sure that your staff have the ability to view Staff Files. You can configure this in permissions - navigate to **Admin Settings** -> **General Settings** -> **Roles and permissions**
Once you've enabled permissions, you can get started setting up categories for your files.
To get started, click **Edit**.
You'll then need to click on **Add a new files category**.
Type in the name of category (i.e. training as per the example below) and then a description of the files that you'll be adding to this folder. You can then add the initial files to this category by dragging the file into the file box or by browsing to upload.
If you choose to save without uploading a file, you'll now see the Training Category as per below.
You can go then go through and add in additional categories in the same way - basically giving you a way to organize files for your staff to easily find.
Once you've setup your categories, hit edit again and start uploading your docs. Just remember the 5MB file size and you should be good to go.
---
# 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://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/staff-files-an-overview.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.