One mini-course or a collection? Group lessons by audience and upkeep

Group by the learner’s job, not your folder structure

A single course can handle one meaningful decision. A collection can give learners a reusable place to return to related courses. Neither should reproduce every folder in an operations drive. Start with what the reader is trying to accomplish and which material they are entitled to see.

For a fictional office-coordinator induction, room requests and visitor sign-in might belong together if the audience, access and review owner match. A manager-only exception-approval lesson does not automatically belong there just because it concerns the same building. Relevance and authorization are separate checks.

Complete a grouping card before adding content

• Audience: who needs every lesson in this group, and who should not see it?
• Purpose: what recurring job does the collection support?
• Owner: who can approve a changed rule across the included lessons?
• Access: do the lessons need the same gate?
• Order: is there a real prerequisite, or can readers choose the relevant task?
• Review: which source changes would trigger updates, and can one owner track them?

If one answer differs materially, split the group or document how that difference is handled. Do not create separate collections merely for cosmetic categories when the same learners would be sent through redundant access steps.

The collection boundary can change who gets access

Mini Course Generator’s email and invitation documentation says those access settings apply to the collection. Its guidance for applying a different boundary to one course is to place that course in a separate collection. Check the consequence for all included courses before a move or access change.

This is why “we will organize it later” can become a costly shortcut. If ordinary induction and restricted approval guidance are mixed at the start, tidying the labels will not repair the access design. Write the allowed audience alongside the content plan.

Give learners a return destination they can recognize

The documented collection Share panel provides a collection link. Keep that ordinary return destination distinct from a one-time verification message. Name it for the reader’s job, such as “Office coordination practice,” and explain which lesson to start with. A collection containing three unexplained titles is still a navigation problem.

For the fictional induction, use a short route description: start with room requests if you book rooms; use visitor sign-in when covering reception; consult the current source procedure for an exception. Do not imply that completing the collection grants authority to approve exceptions.

Keep changes local and visible

A useful maintenance register has one row per lesson: decision, source version, owner, audience and last substantive review. When the room-overlap rule changes, update that lesson and any summary that repeats it; leave unrelated visitor instructions alone. Use the impact map rather than duplicating the whole collection for every small edit.

If the group keeps growing without a shared reader purpose, divide it by job and create clear links between the relevant entry points. If there is only one short lesson and no return journey, a direct course link can remain the simpler choice.