## Overview The Open Beta for GitLab Secrets Manager broadens access beyond the closed beta cohort, allowing a wider set of customers to use the feature ahead of GA. The goal is to validate feature completeness, operational stability, and user experience at scale while continuing to gather structured feedback to inform final GA readiness. This epic tracks the readiness criteria, open items, and coordination needed to launch and run the Open Beta successfully. ### Goals * Ensure system holds up under broader, real-world usage * Feature completeness - confirm all planned capabilities are working as expected * Installation experience - confirm installation process is documented and no challenges * Participation - at least 20 customers participating in open beta * GA readiness - gather feedback to inform final GA launch ### Features Available in Open-Beta See current scope of Open-Beta features [here](https://gitlab.com/groups/gitlab-org/-/work_items/10723#delivery-goals) ## Scope #### **Opt-in Experience** | DRI: Joe, Jaclyn, Fabien - [Design](https://gitlab.com/gitlab-org/gitlab/-/work_items/597481/designs/Self-managedEnable_SM_open_beta.png) * [ ] **GitLab.com:** Top-level group toggle to enable Secrets Manager for subgroups and projects. Instrumentation event fires on toggle. * [ ] **Self-Managed:** Instance-level toggle to enable Secrets Manager for subgroups and projects. Instrumentation event fires on toggle. * [ ] **Dedicated:** Not supported. * [ ] **Prerequisite:** Premium and Ultimate Customers * [ ] **Transition Plan to GA:** Opt-in and communication plan for open-beta to GA cohort. #### **Engineering** | DRI: Mark M, Fabien * [ ] Identify a data transition path from beta to GA. --- ## Enablement #### **Pricing Communication** | DRI: Joe, Sarah * [x] Define messaging that customers opting in will be charged at GA * [x] Review with Legal * [ ] Update relevant docs and in-app messaging to reflect paid status at GA. #### CRM Reporting | DRI: Joe - [ ] Report on customer opt-ins and share weekly summaries with the field. #### Field Enablement | DRI: Mark Settle / Joe - [Activities](https://docs.google.com/document/d/1iqONs7VKKFTGaq9Xv2SRrmQqHR1yfXQnUVEd4XNXFIs/edit?tab=t.ijp19jhkghy0#heading=h.t3qamzu1dk1b) * [ ] Release post item with in-app anouncement * [ ] Blog post with messaging and video * [ ] Send communication to the field on Open Beta availability. * [ ] Produce a one-pager covering capabilities and proposed pricing. * [ ] Create a public Slack channel for Secrets Manager updates and question * [ ] Internal enablement with CS and AEs to drive beta participation #### Documentation | DRI: Marcel * [ ] Instructions for enabling Open Beta on Self-Managed and GitLab.com. * [ ] Usage pricing communication (aligned with Pricing Communication output). #### Feedback & Participant Engagement | DRI: Joe, Jaclyn - [ ] Promote internal usage and adoption - [x] Open a public issue to collect feedback from Open Beta customers.