From ba03eeb35ffdc2f1420bdf6dd425a66decc1ebe2 Mon Sep 17 00:00:00 2001 From: russell-loube-mixpanel Date: Fri, 16 Oct 2026 16:12:41 -0400 Subject: [PATCH] docs(featureflags): remove coming soon tag from overall flag permissions Co-Authored-By: Claude Opus 5.5 --- docs/featureflags.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/featureflags.mdx b/docs/featureflags.mdx index bd88e251..823c4a02 100644 --- a/docs/featureflags.mdx +++ b/docs/featureflags.mdx @@ -234,7 +234,7 @@ We recommend establishing light-weight controls without slowing teams. ### Permissions - **Project Role** — you need to have at least an “analyst” role to create and edit feature flags. “Consumer” roles can only view feature flags. - - \[coming soon\] Overall Feature Flag permissions - this setting allows you to give users or teams access to all feature flags. It overrides the permissions set at a per-flag level. For example, you might want your ops-lead team to have edit access to all flags for emergencies. + - **Overall Feature Flag permissions** - this setting allows you to give users or teams access to all feature flags. It overrides the permissions set at a per-flag level. For example, you might want your ops-lead team to have edit access to all flags for emergencies. - **Feature Flag Permissions** — You can manage share settings per flag.. Only editors for a flag will have access to modify a flag generally. ### Audit Trail