Activate approvals for a project
Only users with Admin rights can configure approvals. To activate flag approvals:- Click Features > Flags & Experiments in the left sidebar.
- Click the Settings tab, then select Approval settings.

- Select the project for which you want to enable flag approvals from the dropdown.
- Select the users who can review requests, then click Save.
If you select the option to trigger approvals only for the production environment, Kameleoon applies the workflow only to the environment with the key
production. However, changes that indirectly affect the production environment—such as updates to variables, variations, or goals—also trigger the approval workflow.Approvals don’t control environments, integrations, or the flag toggle. Only users with Production permissions can change a flag’s state (on/off).
Request approval for flag changes
After you activate approvals for a project, non-reviewer users see an approval request popup when they save their changes. You can customize the title of the request and add a comment that the approver can see.
Approve change requests
On the main dashboard, approvers can see an overview of each flag’s review status:
- Pending: The flag has at least one pending request.
- Reviewed: All requests have been either approved or rejected.
- Pending: Awaiting review.
- Approved: The change has been approved and applied.
- Rejected: The change was declined.
- Invalid: The requested changes are no longer applicable because of more recently applied changes. Kameleoon rejects this request by default.
Approvers can only review requests in top-down order (newest request first).
FAQs
Can a flag be exempt from the approval process?
Can a flag be exempt from the approval process?
No. After you enable approvals, all flags in a project must go through the approval workflow. If the process seems too stringent, consider revising the list of approvers.
What happens to rejected requests?
What happens to rejected requests?
Kameleoon discards rejected requests, but requesters can always resubmit their changes.
What if users request conflicting changes or change the same value or entity?
What if users request conflicting changes or change the same value or entity?
A newest-first review process ensures that invalidated requests are flagged and ignored, eliminating any risk of data conflicts.