mirror of
https://github.com/Unleash/unleash.git
synced 2024-10-18 20:09:08 +02:00
e7ef06ff9d
This change updates the "change requests permissions" section of the change request doc to explicitly call out a few things we've seen confusion around recently. These are: - project owners can't approve/apply change requests. You must create custom roles - viewers can create change requests. This is intentional - skip change requests only works via the API It also: - elaborates a little on the circumventing change requests section to clarify how it works. - adds the change requests project roles to the project roles list. This section should be kept up to date with all the relevant roles that exist for projects. |
||
|---|---|---|
| .. | ||
| addons | ||
| api/legacy/unleash | ||
| deploy | ||
| integrations | ||
| sdks | ||
| activation-strategies.md | ||
| api-tokens-and-client-keys.mdx | ||
| archived-toggles.md | ||
| change-requests.md | ||
| custom-activation-strategies.md | ||
| environments.md | ||
| event-log.md | ||
| feature-toggle-types.md | ||
| feature-toggle-variants.md | ||
| feature-toggles.mdx | ||
| front-end-api.md | ||
| impression-data.md | ||
| maintenance-mode.mdx | ||
| network-view.mdx | ||
| playground.mdx | ||
| projects.md | ||
| public-signup.mdx | ||
| rbac.md | ||
| segments.mdx | ||
| service-accounts.md | ||
| sso.md | ||
| stickiness.md | ||
| strategy-constraints.md | ||
| tags.md | ||
| technical-debt.md | ||
| unleash-context.md | ||
| whats-new-v4.md | ||