### Problem to solve Currently [Audit Events](https://docs.gitlab.com/ee/user/compliance/audit_events.html) are all [streamed](https://docs.gitlab.com/ee/user/compliance/audit_event_streaming.html) and some are stored in GitLab and can be viewed in the [audit event reports](https://docs.gitlab.com/ee/user/compliance/audit_events.html#viewing-audit-events). There are columns in our [audit events types](https://docs.gitlab.com/ee/user/compliance/audit_event_types.html#available-audit-event-types) docs which indicate whether the audit event is **Saved to database** and/or **Streamed**. Currently, all audit events that are **Saved to database** are retained indefinitely. Because there is no retention timeframe, all audit events are available. We are planning on adding a retention in https://gitlab.com/groups/gitlab-org/-/epics/7917+. But some user do not want any/some audit events saved to the database and will only use streaming audit events. Due to the amount of audit events that can be created this can also create storage issues. ### Proposal Provide users with a way to selectively configure whether audit event types are saved to the database or not. All audit event types will still be streamed. A new permission may need to be scoped so that only a certain number of persons or a person is allowed to toggle this setting. ### Risks If users do not stream audit events out using a SIEM and they decide to not save any audit events in a database by turning this toggle on, that means that there are no audit events saved for them at all. This runs the risk of them failing their compliance obligations under a number of different compliance frameworks + standards, as well as being deprived of key evidence that is the accepted norm for auditors these days in order to pass routine and regular compliance audits <!-- 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 -->