- handbook
- Company
- Company
- Board & Investors
- Communications
- Decision making and project management
- Guides
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Incident Response Plan
- Cryptography Policy
- Secure Development Policy
- Data Management Policy
- Access Control Policy
- Information Security Policy and Acceptable Use Policy
- strategy
- values
- Operations
- Product
- Blueprints
- Feedback
- Market Segments
- Metrics
- Node-RED Dashboard
- personas
- Pricing Principles
- Principles
- Responsibilities
- Strategy
- Versioning
- Customer department
- Customer
- Customer Success
- flowfuseforeducation
- Hubspot
- Marketing
- How we work
- Video
- Customer Stories
- Community
- blog
- Lead Generation
- Social Media
- Marketing - Website
- Trade Shows
- FlowFuse Messaging
- Webinars
- Sales
- Engineering & Design Practices
- Design
- Engineering
- Certified Nodes
- Contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Deployment
- Incident Response
- Observability
- FlowFuse Dedicated
- Staging Environment
- Production Environment
- Project Management
- Releases
- Security Policy
- Team NPM Registry
- tools
- Website A/B Testing
- Internal Operations
- People Ops
# FlowFuse Cloud Change Control
We track changes made to either the Staging or Production environments of FlowFuse Cloud through issues on the CloudProject repository.
The issues should record the nature of the change required, which environment it applies to and provide all of the necessary details to enact the change and to verify the change was successful.
- Create a Change Request issue on the CloudProject repository.
- Obtain a review and approval to make the change from Engineering leadership - this should be done as a comment on the issue.
- Assign the issue to the person making the change.
- Once the change has been applied, verify the change is complete
- Close the issue once verified