> For the complete documentation index, see [llms.txt](https://docs.artific.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.artific.nl/en/for-everyone/projects.md).

# Projects

A project keeps related chats, files and background information together in one place.

## What a project is for

A normal conversation with an assistant starts from nothing. That is fine for a quick question, and tiresome when you are working on something over days: you find yourself re-explaining the situation and re-attaching the same documents every time.

A project fixes that. You set the background once and add the relevant files once. Every conversation inside the project starts already knowing them.

Good candidates: a tender you are writing, an audit you are preparing for, a customer account you handle regularly, a report you are drafting over several sessions.

## Creating one

**Projects → Create project**.

| Field         | What to put in it                                                                    |
| ------------- | ------------------------------------------------------------------------------------ |
| **Assistant** | The assistant that will work with you. Only assistants that support projects appear. |
| **Name**      | What the project is called.                                                          |
| **Context**   | Background sent with every message in this project.                                  |
| **Files**     | Documents available in every chat here.                                              |

### Writing the context

This is the part worth spending time on. It is included with every message, so anything you write here you never have to explain again.

> *We are responding to a tender from the Municipality of Example for facilities management, due 14 March. I am writing the quality section. Our proposition is sustainability and local employment. Keep the tone formal and refer to the requirements document by section number.*

Cover: what the work is, what your role in it is, any constraints, and how you want things written. Keep it to what genuinely applies every time.

{% hint style="info" %}
If the assistant does not appear in the list, projects have not been enabled for it. Ask your administrator. See [Getting help](/en/for-everyone/getting-help.md).
{% endhint %}

## Working in a project

Chats appear down the left, with **New chat** above them. The main area is a message box for starting a new one, and your recent chats below.

Start a new chat per sub-task rather than one long thread: *the quality section*, *the pricing annex*, *the covering letter*. All of them share the same context and files, and each stays focused.

Search the chat list to find one again. Where colleagues have access, tabs let you filter between **All**, **Mine** and **Colleagues**.

## Files

Files added to a project are available in every chat inside it. Drop them anywhere on the project screen, or manage them under **Settings → Files**.

Use project files for the material you keep referring to: the specification, the previous version, the guidelines. Use a normal attachment in a single chat for anything you only need once.

## Sharing a project

If you created a project, **Settings → Sharing** controls who else can see it.

**Who can open this project**:

| Option                 | Who gets in                         |
| ---------------------- | ----------------------------------- |
| **Only me**            | Nobody else.                        |
| **Specific people**    | Only the people and groups you add. |
| **Whole organisation** | Everyone in your organisation.      |

**Share chats too** decides whether the conversations are shared or whether everyone only sees their own.

Each person or group gets an access level:

| Level          | What they can do                                 |
| -------------- | ------------------------------------------------ |
| **Chats only** | See the chats, but not the context or the files. |
| **Can view**   | Read the context, the files and the chats.       |
| **Can edit**   | Also change the project and its files.           |

New people start at the narrowest level, which you can raise.

Adding a **group** rather than individuals is usually better for a team: people who join the group gain access and people who leave lose it, without anyone maintaining a list.

{% hint style="warning" %}
Sharing stays inside your organisation. Nothing here creates a public link. Even so, think about what is in the context and files before sharing widely. That is what you are sharing, not just the conversation.
{% endhint %}

### Whose chat is whose

Chats belong to whoever started them. You can read a colleague's chat in a shared project but not reply in it, and only the person who started a chat can rename or delete it, the project owner included.

## Deleting

**Settings → General** has **Delete this project**, available to the owner.

{% hint style="danger" %}
Deleting a project deletes its files and every chat in it, including chats started by colleagues. It cannot be undone.
{% endhint %}