CS-Cart Update Access & Roles
Update Access & Roles
Change Triggers
- Note common reasons to adjust roles (new site launch, feature enablement, seasonal support).
- Capture approvals required before changes proceed.
- Track related tickets or requests for audit history.
Execution Steps
- Outline how to edit roles, groups, or environment permissions.
- Document impacts to API keys, publishing rights, or workflows.
- Record communication templates for notifying stakeholders of updates.
Post-Change Validation
- List smoke tests verifying the new access works as expected.
- Archive updated user lists or audit logs.
- Schedule follow-up reviews if the change is temporary.