Change Management Policy

1. Purpose

This policy ensures that changes to the Seen CRM platform are made in a controlled way that protects its security and reliability.

2. Scope

This policy applies to all changes to the platform's software, databases and configuration.

3. Policy

1. Controlled process. Every change is documented, reviewed and approved before it reaches production.
2. Automated testing. Every change passes automated tests, including security tests and checks for exposed secrets. A failed test stops the release.
3. Approval. Releases to production are approved by management.
4. Database changes. Changes to production databases are reviewed in advance and applied under supervision, with the result verified afterwards.
5. Gradual release. New features are first enabled for a limited group before wider release.
6. Rollback. Every release can be reversed by returning to the previous version.
7. Emergency changes. Urgent fixes follow the same testing and approval controls and are recorded.

4. Responsibilities

The engineering team prepares and tests changes. Management approves releases and production database changes.

5. Exceptions

No change may bypass a failed test. Any other exception must be approved in writing by management, with a stated reason and an end date.

6. Review

This policy is reviewed at least once a year, and after any major security incident.

7. Contact

Questions about this policy: info@seencrm.com