Configure the Systems workspace experience and its vocabulary separately. Settings → Framing controls supported capabilities and fields. Databases → Configuration maintains the catalogue values offered in those fields.
Review system-specific lists
Use the Systems group in the Databases index for types, domains, criticality, accessibility, management, hosting, cloud types and stack components, RPO and RTO where available.
Cross-module lists provide shared context such as architectural domains, business units, functional domains, regions, data classification and CIA levels. Use the live catalogue index to locate a list rather than looking for the retired Configuration Catalogs tab.
Maintain clear choices
Define each choice in language the team can apply. For recovery objectives, agree the operational meaning of the value before using it in assessments. For hosting and management, distinguish where the component runs from who is responsible for operating it.
Edit a catalogue entry through its own editor and choose Save. Hide an entry when it should leave future pickers but remain understandable in existing records. Hiding does not delete the system records that already use it.
Check access and effect
Catalogue configuration uses Catalog Management permissions. Controls and Threats library access uses the separate Databases Management capability. Editing a system itself requires the applicable System Management or accepted record-specific access.
Framing switches apply immediately and do not grant permissions. Catalogue edits also have their own save scope; they are not included in an open system record's pending save bar.
After a material change, inspect an affected system and review whether existing classifications remain meaningful. Explain changed definitions to assessors before comparing records classified under different criteria.