- 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
- Access Control Policy
- Information Security Policy and Acceptable Use Policy
- Data Management 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
- FlowFuse for Education
- Hubspot
- Marketing
- How we work
- Video
- Customer Stories
- Community
- blog
- Lead Generation
- Social Media
- Marketing - Website
- Webinars
- Trade Shows
- FlowFuse Messaging
- Brand Voice
- 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
As part of our secure operations policies we implement a Change Control process for certain operations in order to provide auditable, reviewable changes to key systems.
The following tasks should be completed under change control.
# 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
- 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
# FlowFuse Dedicated Instance Change Control
Changes to customer dedicated instances managed by FlowFuse should follow the same process as listed above for FlowFuse Cloud. The one difference is that the details of exactly which instance the changes should be applied to.
# Access / Permission Request
Where access is required to a system, a Access / Permission Request issue should be created in the admin repository.
Note: when onboarding/offboarding a new employee, this is managed via the Onboarding/Offboarding change request.
# New GitHub Repository
If a new repository is required within our GitHub organisation, a New Repository Checklist issue should be created in the admin repository.
# Onboarding/Offboarding
When bringing a new employee into the company, or saying goodbye to an existing one, the appropriate Onboarding or Offboarding issue should be created in the admin repository
More details around Onboarding is available in the Hiring and Onboarding section of the handbook.