- handbook
- Company
- Company
- Board
- Communications
- Decision making
- 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
- Access Control Policy
- Incident Response Plan
- Cryptography Policy
- Information Security Policy and Acceptable Use Policy
- Secure Development Policy
- Data Management Policy
- strategy
- values
- Operations
- Product
- Feedback
- Market Segments
- Metrics
- Node-RED Dashboard
- personas
- Pricing Principles
- Principles
- Responsibilities
- Strategy
- Versioning
- Customer department
- Customer
- Customer Success
- Hubspot
- Marketing
- How we work
- Marketing
- Video
- Customer Stories
- Social Media
- blog
- Community
- Marketing - Website
- FlowFuse Messaging
- Webinars
- Sales
- Engineering & Design Practices
- Design
- Engineering
- Certified Nodes
- contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Deployment
- Incident Response
- Observability
- Production Environment
- FlowFuse Dedicated
- Staging Environment
- Project Management
- Releases
- Security Policy
- tools
- Website A/B Testing
- Internal Operations
- People Ops
# Accounts
As a company we use a variety of online services in our day-to-day business.
Access to the services is subject to our access control policy.
When new team members join the company, access will be provided to the core services in accordance with our onboarding process.
To request additional access to any service, follow the guide here.
# FlowFuse Cloud
These are the principles of how we setup and use accounts on the FlowFuse Cloud platform.
Shared accounts should be avoided wherever possible, particularly on our own systems as this removes the ability to track which individual made a change.
# User Accounts
All employees of FlowFuse should have a user account on FlowFuse Cloud and be added to the FlowFuse Team in order to access our own company projects. This is part of the onboarding checklist.
The email address for this account should be their normal @flowfuse.com address and will make use of single-sign on.
# Internal Teams and Contracted revenue
Any teams created by employees must have billing disabled to avoid polluting our revenue tracking. This is achieved by placing the team into 'manual' billing mode.
For customers on contracted revenue, e.g. an annual deal made by an account executive, the team too is put into manual billing mode.
- Raise a Change Request with the name of the team and a request to move it to manual billing mode
- The request can be actioned by anyone with admin access to the platform. They will have access to admin-only tools on the Team Settings/Danger page, including the option to 'Setup Manual Billing'. As part of this process, they can pick what Team Type should be applied. Unless specifically requested otherwise, teams should always be upgrade to Enterprise to ensure they have full access to all features.
# Admin
Where their role requires it, an employee's account may be provided admin level access. This can be achieved by raising an access request with details of the request.
A dedicated Admin account also exists - details are available in 1Password.