Collections: keep the documents for a job together

Collections are GPTree's folders. Use one to keep the documents for a job together: the contracts for one client, the sources for one report, the pages a new starter should read first.

Making one

On a computer, the Knowledge page has a panel on the left with a Collections section. Choose + New, type a name, and choose Create. The collection appears in the list with a count of its documents. A phone does not show that panel, so make collections on a computer.

Adding documents

Open one of your documents, pick a collection under Add to a collection, and choose Add. To add several at once, tick them in the list, pick a collection from Add to a collection in the bar that appears, and choose Add. A document's panel lists the collections it is in.

A document can sit in as many collections as you like: your employee handbook can be in both HR and Onboarding without making a second copy, which matters because a copy would have its own separate history.

Click a collection in the panel to see only its documents, and click it again to go back to everything.

Projects need no filing at all. The same panel lists each of your projects, and a file added to a project shows up under it the moment it lands.

What a collection changes, and what it does not

A collection is for finding and organising. It does not change what a chat reads. A chat inside a project reads that project's files and can cite them, and a file you attach to a message is read in that conversation. To have chats read one of your documents, put it in a project: open the document and choose the project under Belongs to.

Reading and citing a project's own files works on every plan. Whether a chat outside a project can also search the rest of your knowledge depends on your plan. Open a document on the Knowledge page and it tells you what chats do with it.

When an answer cites a document that is in one of your collections, the citation's panel names the collection, so you can see which job the source belongs to.

Your collections are yours. Nobody else sees them, and putting a document in one does not share it with anyone. Sharing with your workspace is its own deliberate act: putting a document in the company library.

What GPTree writes for you

Reports your agents write, crew outputs and conversations you save all appear in Knowledge, and you can read, compare and keep them. When a chat searches your knowledge for an answer, it does not use them as sources. That is deliberate: otherwise an answer could quote an earlier answer back to you as though it were evidence, and a mistake made once would harden into a fact.