Ally.io is now the [Single Source of Truth for OKRs](https://about.gitlab.com/handbook/product/product-okrs/#product-okrs). Please see that system for OKRs. <details><summary>Old issue content</summary> # Overview This issue is intended to document the [Product Hive](https://about.gitlab.com/handbook/product/product-processes/#quad--infra--security-hive-dris) for Manage::Compliance's OKR for FY22-Q3. This is based off the new pilot process in the [handbook](https://about.gitlab.com/handbook/product/product-okrs/#fy22-q3-product-okr-process). [Product org OKRS](https://gitlab.com/gitlab-com/Product/-/issues/2715) [[_TOC_]] # OKR ([Ally.io link](https://app.ally.io/objectives/1493036?tab=undefined&time_period_id=135092) to the same OKR) ## Objective **Enable compliance-conscious customers to confidently choose GitLab.com for their DevSecOps platform.** ## Key Results | Key Result | Progress | Epic/Issues | Rationale | | ------ | ------ | ------ |------ | | Deliver the ability for users to easily see the list of users and what access they have in their GitLab.com groups. | 0%| [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/287940) | Understanding access to projects and groups is a commonly heard use case for our users. Without the ability to do this on .com, there is additional friction that may cause users to stick with self-managed. | | Deliver three new audit events that surface information that was previously only available at an instance level. |0%| [1](https://gitlab.com/gitlab-org/gitlab/-/issues/6831), [2](https://gitlab.com/gitlab-org/gitlab/-/issues/8071), [3](https://gitlab.com/gitlab-org/gitlab/-/issues/300961) | Visibility into what is happening inside GitLab is critical for being able to pass audit successfully. If we have information that is only available at the instance level, this puts a barrier to adopting GitLab.com. | | Deliver the ability to enforce settings on Merge Requests for a root group and all subgroups below it. | 0%| [epic](https://gitlab.com/groups/gitlab-org/-/epics/5957) | Setting policies for the entire organization allows compliance teams to confidently move through audits, since they know that teams are following required steps. This is possible today on self-managed, but without the same ability on GitLab.com, teams are less confident and so may choose to remain on self-managed.| ## Details This OKR rolls-up to support the overarching theme of "Adoption Through Usability" and "SaaS First". # Engineering OKR ## Objective Support each other and ourselves. ## Key Results | Key Result | Progress | Epic/Issues | Rationale | | ------ | ------ | ------ |------ | | Hire 2 Backend Engineers | 0% | [Greenhouse](https://gitlab.greenhouse.io/plans/4870250002/candidates?hiring_plan_id=4870250002&stage_status_id=4000006002) | To achieve our ambitious goals, we need capable software engineers to help us build our vision. | ## Objective Maintaining strong productivity. ### Key Results | Key Result | Progress | Epic/Issues | Rationale | | ------ | ------ | ------ |------ | | Maintain MR Rate of 8+ | 0% | - | MR Rate is considered a measure of productivity. | </details>