Use shared catalogues to maintain the vocabulary used across your workspace. Open Databases, then choose a catalogue from Configuration in the left index. Expand a group or use Filter configuration catalogs to find a list.

Review an entry

Select a row to inspect its details. The available fields depend on the catalogue. A detail may show its name, description, origin and whether it is shown in workspace pickers. View original, where available, displays the underlying reference wording.

Treat an unavailable usage count as unknown. A dash does not prove that an entry has no users or dependencies. Check the relevant business records before making a change with wider consequences.

Change workspace entries

  1. Confirm the active workspace and select the intended catalogue.
  2. Open the entry and choose Edit, when available.
  3. Update the supported fields and choose Save in that editor.
  4. Wait for confirmation and check the refreshed entry.

The entry editor saves that record directly. Cancel closes an unsaved edit. It does not undo a previous successful save or a separate visibility action.

Use the available add action to create a workspace-specific value. Use Hide here when an existing choice should stop appearing in future pickers. Restore its visibility if the team needs it again. Existing records retain their stored values when an entry is hidden.

Reference-governed rows and read-only catalogues have additional restrictions. For example, the CyFun catalogues marked Read only cannot be edited through the normal catalogue editor. The actions on the selected catalogue are the authority for what is currently supported.

Understand access

Configuration catalogue access is governed by Catalogs permissions. Databases permissions separately govern the Controls and Threats reference libraries. Being able to browse one area does not automatically grant editing in the other.

An unavailable editor can therefore reflect your permissions or the catalogue's own read-only status. Ask a workspace administrator to check the effective role permissions when you need access.

Review cross-module changes

Lists such as Business Units, Data Classification Options, Functional Domains, Architectural Domains and Regions can support several modules. Agree definitions before broad use and review the affected workflows before renaming established entries.

Weighting levels also lives under Cross-module, but uses its own editor and save behaviour. Its scale is shared by framework elements and policy controls; see the module catalogue guide before changing it.