Skip to content

Commit 5d40643

Browse files
Apply suggestions from code review
Co-authored-by: Gastón Fournier <[email protected]>
1 parent c06db48 commit 5d40643

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

website/docs/feature-flag-tutorials/use-cases/security-compliance.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Consider this scenario: your company is undergoing its annual security audit, an
8282
- An approval chain is in place to change critical features.
8383
- Sensitive projects remain visible only to appropriate teams and/or project owners.
8484

85-
Unleash is built with many mechanisms in place to handle all of these scenarios. Our systems enforce strict separation of duties, for example, where developers can create and test flags in development environments, while only senior engineers can promote changes to staging.
85+
Unleash is built with many mechanisms in place to handle all of these scenarios. Our systems enforce strict separation of duties, for example, where developers can create and test flags in development environments, while only senior engineers can promote changes to staging and production.
8686

8787
- We leave audit trails, automatically [logging every permission change](#audit-manual-and-automated-events-in-unleash) with detailed user information and timestamps.
8888
- You can set up [approval guardrails](#use-a-change-management-workflow-for-auditing) for feature flag updates.

0 commit comments

Comments
 (0)