To propose changes, you can lock the code list, crosswalk or hierarchy. When you lock the code list, the crosswalk or the hierarchy, a draft version is created and you prevent other users from making changes. You can import, create, update, or delete code values in a code list, value mappings in a crosswalk, and create, update, or delete parent or child code values in a hierarchy. Your edits remain in the draft, and you can choose to continue editing later. The presence of a lock icon beside the code list, the crosswalk, or the hierarchy indicates to other users that you are working on it.

After you finish editing the code list, the crosswalk or the hierarchy, you can send your draft for approval. This action triggers an approval workflow and generates an approval task. Users responsible for approving the task receive notifications. As the code list, the crosswalk or the hierarchy progresses through the approval workflow, it remains locked.

Users assigned the following roles can send their proposed changes for approval or directly publish their changes without approval:

Reference 360 Primary Owner role and the Primary Owner stakeholder role for a code list.
Reference 360 Business Steward role and the Business Steward stakeholder role for a crosswalk.
Reference 360 Planner role and the Planner stakeholder role for a hierarchy.

For more information about roles, see Users, groups, and roles