Community Early Access Programs | Guidelines
Community Early Access Programs (CEAPs) 🚀 Interested to know how these programs work? This is your chance to get exclusive access to a feature that is yet to be released to our wider user-base. The Early Access (EA) program gives you the opportunity to test the feature while sharing feedback and suggestions with fellow community members, for our Product team to review. To start, please ensure you have referred to the key conditions below for the CEAP (Community Early Access Program), including the dedicated Early Access documentation. Early Access: Users gain access to features that are ready to be used, but undergoing fine-tuning - allowing members to explore functionalities ahead of the general public. Testing and Feedback: Members are expected to actively test the features and provide feedback on their experience, including reporting any errors or bugs encountered. No Guarantees: There is no guarantee that features in the CEAP will be released publicly or that all feedback will be incorporated into the final product. Potential for Errors or Bugs: Since features are still being fine-tuned, participants should anticipate encountering errors, bugs, or incomplete functionalities. Release Timelines: Developers do not commit to specific timelines for releasing features or making improvements based on feedback received during the CEAP. Confidentiality: Participants may be required to sign non-disclosure agreements (NDAs) to protect confidential information about the features being tested. How to join? All of our Community Early Access programs (CEAPs) are hosted via Community groups. All CEAPs will be shared via a dedicated Community post under Announcements or referenced in our Community Monthly's - also posted in the Announcements section. In order to express interest in an EA program, please request to join the specific EA Community group and we will approve accordingly. It’s important to note that some early releases will be granted on a first in, first served basis, according to the time in-which you request to join the group. This will be based upon the specific feature and granting limit provided by our internal Product and Engineering teams. Questions? Please comment on this post or reach out to bianca.taylor@safetyculture.io directly!
