What ‘beta’ means for you
In practice, a ‘beta’ feature is:
- One that our engineering team is still actively working on
- Going to evolve, but we’ll let you know if any changes will affect your existing work
- Open to your feedback, should you want to give it
When a feature is in beta, we’ll always shout about it, but we’ll also give you the opportunity to opt-out. This is because while beta features can be new and exciting, they are also not yet 100% stable. Their code and components are complete for the most part, but there may still be some rough edges that you can help bring to our attention. So when you opt-in, please keep this risk in mind and be extra-cautious when using it in anything mission critical.
Send us your feedback and questions!
We want to hear from you! So let us know: Are you missing something you need? Do you see any bugs? Is the feature frustrating to use? Do you see something you like? Anything at all, just let us know via email at firstname.lastname@example.org
To access beta features in Vega, make sure you TURN ON the beta functionality in the Admin - Organisation Profile section.
These are our current and upcoming beta features in Vega:
Just as a reminder, using beta features is at the user's own risk and will not be covered by any service level agreements or our normal terms & conditions. This is an Early Access feature, so there is a small chance there may be issues that pop up from time to time. We don't expect any bugs to inhibit your ability to continue your work. If there are any urgent issues, please contact us via email at email@example.com.