Why this matters
A setting without its purpose can be changed later for the wrong reason.
Step by step
- For an important approved setting, record what task it supports and who owns it.
- Keep non-secret previous values and the reason for the decision in the change record.
- Before a later modification, check whether the original dependency still applies.
Keep the result of the final check and any unresolved question with your project records.
Availability depends on the product, permissions and management agreement. Use the existing support conversation for the same issue.
