Catalogs

A catalog is a named list of approved models. Catalogs decide which models each workspace may add; the workspace's owner or admin then adds the ones it uses.

ExamplesCopy Anchor Link

Catalogs are yours to define. Example University might have:

Create a catalogCopy Anchor Link

Create catalog with a name and description, then add models on its Models tab. A catalog's page also shows Who gets it (the workspace types whose defaults include it, and the workspaces that chose it themselves) and Settings.

You can also set a model's catalogs from the model's own page, under Availability.

Defaults per workspace typeCopy Anchor Link

Defaults is a matrix of catalogs against Personal, Team and Project. Every workspace of that type without its own choice gets exactly those catalogs, and follows changes at once.

A new personal workspace, Team or Project whose type has no default catalog starts with no models. The setup checklist reminds you.

Replace them for one workspaceCopy Anchor Link

On a Team's or Project's page in Admin, under Models, you can replace its catalogs with your own choice. A replacement:

• replaces the type's defaults, it doesn't add to them;
• can be empty, which means no catalog models at all (direct assignments still work);
• no longer follows changes to the defaults, until you reset it.

Direct assignmentsCopy Anchor Link

A Platform Admin can assign a model to one workspace directly, outside any catalog, for exceptions. Direct assignments are independent: losing a catalog doesn't remove them, and removing one doesn't touch catalog access.

What happens when access is removedCopy Anchor Link

When a model leaves a catalog, or a catalog stops being available to a workspace, the workspace loses the models it added from it, unless another available catalog or a direct assignment still covers them.

• Keys restricted to such a model lose it too. A key whose models are all removed can't use any model; it never turns into an unrestricted key.
• Selections removed this way don't come back if the model returns later. The workspace's admin adds the model again, and keys that should use it must be re-created.
• Requests already running may finish.