Collections, Categories, and Organizing Many Documents

The first ten documents in an organization are easy. The fiftieth is harder. The two-hundredth needs structure — categories, collections, sub-categories, language pairs.

This post is about the organizational tools DocuTrain gives you at scale: categories, collections, language associations, and discoverability.

Categories: two-level hierarchy, simple by design

Every document can be tagged with one category. Categories serve three purposes:

• They're how people filter documents on your organization's landing page
• They're how admins find documents in the dashboard
• They're how the gallery layout groups document cards visually

There are two flavors:

System categories

DocuTrain ships with a default set: Guidelines, Manuals, Presentation, Recipes, Reviews, Slides, Training. Every organization can use them.

They cover common patterns. They're a starting point, not a constraint.

Custom categories

You can add your own names — scoped to your organization so they don't appear in anyone else's menus.

Custom categories can sit under a parent (system or custom), but only one level deep: parent → child, no deeper. That keeps things simple in the real world; very deep trees look good in theory and become hard to maintain.

The Categories tab in Owner Settings (super-admin only) is where you create, edit, and delete categories.

Picking a category

When you upload or edit a document, Basic Info includes a category dropdown — system entries first, then your custom ones.

Collections: bundling documents with shared access

A collection is a curated bundle of documents wrapped in its own landing page with its own access control. Think:

• A course made up of multiple training modules
• A clinical specialty area with several related guidelines
• A product line with one document per product variant
• Conference materials bundled for attendees

You build and maintain collections in the collection editor in the dashboard.

What a collection has

Collection chat: ask the whole bundle at once

When collection-wide chat is on, users can talk to every document in the collection in one thread. The assistant pulls relevant passages from across the bundle and cites which document each piece came from.

That's ideal when someone doesn't know which file holds the answer — a learner reviewing for an exam doesn't care which module mentions a dosing table; they want the answer.

Tokenized access

Collections have their own access rules on top of individual documents — and tokens are the most flexible option.

A collection can issue share access with:

• A label for your own records
• An expiry date
• A maximum number of uses
• The ability to revoke

Someone with a valid token can open every document in the collection, including items that are normally internal-only. That's how you share a curated bundle with an outside partner without adding them to your whole team. When the project ends, the token can expire or you can revoke it.

Tokens can be shared as links or QR codes for in-person events.

Why collections instead of just categories?

Categories label documents. Collections package them with shared branding, shared access, and optional bundle-wide chat. Most teams use both: categories for browsing, collections for delivery.

A restricted document stays restricted for normal visitors — but a collection token can open a defined set for someone you've chosen, without changing every document's global access setting.

Language associations

DocuTrain supports English and French at the document level, with a document associations section for linking two versions of the same content.

Practically: someone reading the French guideline can jump to the English version (and back) with their context preserved when possible. It's a simple "these belong together" link — not a full translation workflow, which is usually all bilingual teams need.

Discoverability and search

Per-document discoverability

Each document can be marked discoverable in DocuTrain's platform search when it's appropriate for the public. New documents usually follow your organization's default, so you set policy once.

Sitemap inclusion

Suitable public documents can be included in the site's sitemap so search engines can find them — helpful for marketing FAQs and product docs. Publishing updates the sitemap automatically; you don't maintain it by hand.

Organization-level discoverability

• Discoverable on Signup — Your org can appear when new users join the platform; you still approve who gets in.
• Discoverable in Search (Business+) — Your public catalog can show up in DocuTrain's directory.

That separates "this page should be public" from "we're recruiting random signups" — a consultancy might want SEO reach without open enrollment; a society might want both.

The "I have 200 documents now" workflow

Putting it all together, the structure most mature teams settle into looks like:

1. Categories for browsing — Guidelines, Manuals, Training, plus custom labels for your industry
2. Subcategories when a category gets crowded — e.g. Training → Onboarding, Training → Compliance
3. Collections for delivery — e.g. a "Q1 Compliance Refresher" that bundles seven training docs and is shared via passcode
4. Tokens for external partners — issued from the collection, with expiry and use caps

Plus:

• Language pairs when you ship the same material in more than one language
• Discoverability flags when you want (or don't want) directory and search visibility

That's everything DocuTrain gives you for organizing documents. The next post in the core series covers what's gated behind which plan tier, plus integrations like Telegram, email, embed widgets, and custom domains.

→ Next: Plans, Quotas, and Integrations