<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> Accurately tracking GitLab events on an instance is a security feature and is of critical importance for enterprises, especially ones that operate with strict traceability requirements. While we currently track certain events in Audit Events, our goal should be to record ~100% of events for administrators and auditors to evaluate in a single source of truth. This epic covers group settings changes. Items in the following list are missing from the audit events table, and should be added: #### Group settings 1. General 1. [x] Permissions - https://gitlab.com/gitlab-org/gitlab/issues/8051 1. [x] Checkboxes (e.g. allow users to request access, member lock, etc.) - https://gitlab.com/gitlab-org/gitlab/issues/8051 1. [ ] Badges - https://gitlab.com/gitlab-org/gitlab/issues/8066 1. CI/CD 1. [ ] Variables - https://gitlab.com/gitlab-org/gitlab/issues/8070 1. [ ] Runners - https://gitlab.com/gitlab-org/gitlab/issues/8074 1. [ ] LDAP - https://gitlab.com/gitlab-org/gitlab/issues/8072 1. [x] SAML SSO - https://gitlab.com/gitlab-org/gitlab/issues/8071 1. [ ] Webhooks - https://gitlab.com/gitlab-org/gitlab/issues/8068