Working with Collections and Categories

When you open the Browse panel, you'll see two filter options on the left side, Collections and Category.

These are two options that our Business ane Enterprise-level clent teams can use for organizing content to make it easier to find in your authoring site.

They're pretty similar, and they’re intentionally loosely-defined so organizations can use them however it makes sense.

An example use for Collections is to collect the courses in a curriculum together, maybe based on the target audience. So, if you have 5 courses for onboarding new employees, make a Collection named for that and add those 5 into it. Or maybe you have different curricula for  internal emplyees, external clients and contractors. Create a Collection for each of these then asign their respective projects to them, like this example:

Categories might be a way gather together all the content of a similar topic type:

A Project can be added to a Collection as well as a Category (or more than one Category). They’re filters on the Project list, not hard walls or connections.

And there’s no rule that says you need to use both Collections and Categories. The goal is to make it easier for authors to quickly find content that is related/connected, rather than having to search for everything separately or scroll endlessly through the Browse list.

Only Admins can create Collections and Categories but all authors can assign a Project to them.

To create a Collection or Category, an Admin can open the Aplication Menu on the ribbon then select the Organization option on the left menu. There are sepearate options for creating either a Collection or a Category:

There is a subtle difference between Collections and Categories.

You can create as many Collections as you need, but a Project can only be assigned to one of them.

But Projects can be assigned to as many Categories as needed, and each Category is available as separate option on the Project Properties panel. Plus, Categories also have an option for sub-categories.

Admins can Disable a Category or Collection. This has no effect on the projects within it – it just disables the Category or Collection as a filter so it's no longer available on the Browse panel.

Authors can assign a Project to a Collection or Category from the Project Properties panel. 

Here are the steps to do that: