Staffbase offers three different types of deployment for features in the major and minor releases. The appropriate deployment, or rollout, strategy for a feature is determined by the product team and associated stakeholders. You are always notified of any new feature or update and its associated deployment strategy through the Staffbase release process.

The three deployment strategies are:

• Staged rollout
• Activation
• Automatic rollout

Staged Rollout

In a staged rollout, Staffbase gradually releases the feature to its customer base in phases. This method helps the Staffbase Product team manage risk and monitor performance with smaller groups of users. It also allows our teams to observe how the update performs in a controlled environment. If no major issues are detected, the rollout is incrementally expanded. This phased approach ensures a smoother experience when the update reaches all users and allows for quick adjustments if needed. The specifics of staged rollouts, such as timing and scope, vary depending on the feature and other factors. 

Activation

In an activation-based deployment, a feature is delivered to the platform but remains inactive until it is enabled for your organization by Staffbase. This means the feature is present but not available to your platform until it is enabled. This allows you to control which features your platform has activated. You can request activation by contacting your Customer Success Manager or Staffbase Support. All Staffbase beta features are available only by activation.

Automatic Rollout

In an automatic rollout, the feature is automatically activated on your platform during the release. This applies only to features or products you have already activated for your platform. New features or products that you do not already have, are not automatically rolled out to your platform during a release. Automatic rollouts help keep your platform up to date, improving security, stability, and access to new features.