Collections are named groups of files — folders, essentially. They live inside a vault, nest as deeply as you want, and exist for one reason: to keep your vault organized so you can find things quickly. Your Digital Twin still searches across every included file regardless of folder, so a Collection’s job is purely human-facing.Documentation Index
Fetch the complete documentation index at: https://docs.praxis-ai.com/llms.txt
Use this file to discover all available pages before exploring further.
Use Collections to mirror how you think about the content — by topic, course, project, client, or release. A clean vault is a vault you’ll actually trust.
Creating a Collection
Name it and pick an optional color
Color codes show up on the folder icon and on file-card breadcrumbs throughout the vault.
Adding files
You have three ways to put files into a Collection:Drag and drop
Drag any file card onto a Collection card to move it in. Drag from inside a Collection onto the breadcrumb to move it back out.
Multi-select drag
Check the boxes on several file cards, then drag any one of them — the whole selection moves together.
Move to Collection
From the file action menu (or the bulk-action toolbar), pick Move to Collection and select the target from a dropdown.
Moving files between Collections
Just drag the file card from one Collection to another. To move several files at once, multi-select first.Renaming and deleting Collections
Click the ⋮ menu on a Collection card for the management actions.| Action | What happens |
|---|---|
| Rename | Updates the Collection name everywhere it’s referenced. Files inside are unaffected. |
| Recolor | Updates the folder color. |
| Download as ZIP | Archives the Collection and its sub-collections, preserving folder structure. |
| Delete | Deletes the Collection and every file inside it, recursively into sub-collections. |
Nested Collections
Collections can contain other Collections — nesting is unbounded. Drag one Collection onto another to make it a sub-collection. The folder hierarchy shows up in file breadcrumbs everywhere:Courses › Fall 2026 › Biology 101 › Lecture Notes) where each level adds context.
Sharing Collections
If you’re an admin in your institution, you can publish Collections to shared scopes:| Scope | Visibility |
|---|---|
| Personal (default) | Only you. |
| Instance | All users in your institution. |
| Account | All users across every institution in your account. |
Moving a Collection to a shared vault
From inside My Files, drag the Collection card onto the Instance Files or Account Files tab header. The Collection and every file inside it (including sub-collections) move to that scope in one operation. Once published:- Users on the target scope see the Collection in their Instance Files or Account Files tab.
- File-level access tiers (Public / Private / Confidential) still apply — moving a Confidential file to Instance does not make it visible to others; it stays owner-only.
Bringing a Collection back to Personal
Same gesture in reverse — drag the Collection from Instance or Account back onto the My Files tab. The Collection becomes personal again, visible only to you.Permissions on shared Collections
When a Collection lives in a shared vault, who can do what depends on your role:| Role | Add files | Rename / Recolor | Move files in/out | Delete | View |
|---|---|---|---|---|---|
| Instance admin | Yes | Yes | Yes | Yes | Yes |
| Account admin | Yes (Account scope) | Yes | Yes | Yes | Yes |
| Standard user | No (unless granted) | No | No | No | Yes |
Need permission to manage a shared Collection? Ask your institution admin to grant you the appropriate role — Pria’s permission model lives in your Instance Settings.
Using Collections in chat
Collections can do double duty: instead of letting your Digital Twin search the entire vault, you can restrict retrieval to a single Collection for focused answers. This is useful when:- You’re working on a specific project and want answers grounded only in that project’s files
- You have overlapping topics across Collections and want to disambiguate
- You’re testing how a Collection’s files behave in conversation
Organization tips
One Collection per project
Resist the urge to over-nest. A project Collection with everything inside (sources, notes, deliverables) is easier to scope than three levels of folder hierarchy.
Archive old Collections
Use a top-level
Archive Collection for finished work. The files stay searchable, but they don’t clutter your current view.Color-code by intent
Use folder colors consistently — e.g. blue for active, gray for archived, red for sensitive. Color carries through breadcrumbs and file cards.
Watch for orphans
Files at the vault root with no Collection are easy to lose track of. Run a quick sort by date occasionally and tuck recent uploads into the right Collection.
Use the Display filter
Combine Collection navigation with the Display: Processing or Display: Error filter to find files that need attention inside any Collection.
Don't fight the search
Remember: your Digital Twin searches across every included file regardless of folder. You don’t need Collections for retrieval to work — they’re for you.
Related
- IP Vault — vault overview, access tiers, and what each vault is for
- Managing Files — uploads, file actions, bulk operations
- Searching Inside Your Files — content search and Collection-scoped queries
- Knowledge Modes — how Pria uses your Collections at chat time