Overview
Change control helps keep your Tines tenant stable, secure, and predictable, especially as more users build and update stories. These best practices ensure that every change is reviewed, documented, and aligned with your team’s standards before going live.
Best practices
Enable change control
Enable change control for the entire tenant. Change control incorporates peer reviews before changes go live to help catch mistakes, prevent unintended impacts, and uphold shared quality standards. This safety net is especially critical in production environments where changes could affect automation outcomes.
Manage change control requests
Use a Tines story to manage change control requests. Route the change control approval requests to a group of trusted Tines platform owners for review. Document change control requests in a tracking system like records.
Automating and standardizing the change control process ensures consistency in reviews, tracking of approvals, and documentation of decisions. This provides a reliable audit trail for future reference or compliance needs.
Note: If you have access to custom roles, you can fine-tune who can manage change requests. Considering a low tolerance of risk, we recommend creating a custom role with all editor permissions except for change control so the users cannot approve changes outside of your defined process.
Establish standards
Create standardized guidelines to review against change requests and document them for all story builders and reviewers.
This checklist gives builders and reviewers a clear, consistent framework to evaluate changes against. It helps maintain high standards across the board, reduces the chance of inconsistent updates, and ensures everyone is aligned on what “excellent” looks like.