User roles

Understand Kameleoon’s role-based permission system, including what each role (Super Admin, Admin, Technical, Marketing, Production) can view and modify.

Kameleoon uses roles to control what each user can view or modify within a project. You assign roles per user and per project. If a user has multiple roles, Kameleoon merges their permissions and grants the combined access.

For example:

• Marketing + Production → a user can manage campaigns and launch them.
• Technical + Marketing + Production → a user can create campaigns, configure advanced options, integrate tools, and launch campaigns.

Roles

Role	Description
🛡️ Super Admin	Manages account-level administration and user access
⚙️ Admin	Manages project configuration and integrations
🧑‍💻 Technical	Handles technical setup and integrations
📈 Marketing	Creates and manages experiments and personalizations
🚀 Production	Launches campaigns and manages production rollout

---

Account administration permissions

These permissions apply to account and project management, including users, teams, projects, activity logs, and integrations.

Permission	🛡️ Super Admin	⚙️ Admin	🧑‍💻 Technical	📈 Marketing	🚀 Production
Create, deactivate, reactivate, or delete users	✅	❌	❌	❌	❌
Configure user rights	✅	❌	❌	❌	❌
Add users	❌	✅	❌	❌	❌
Access the Teams page	❌	✅	✅	✅	✅
Edit a project	❌	✅	✅	❌	❌
Access the Project page	❌	❌	❌	✅	✅
Access the Activity page	❌	❌	❌	✅	❌
Manage integrations	❌	✅	✅	❌	❌

---

Shared permissions

These permissions apply to both Web Experimentation and Feature Experimentation.

Permission	⚙️ Admin	🧑‍💻 Technical	📈 Marketing	🚀 Production
Manage advanced tools	✅	✅	✅	❌
Access audience insights	❌	❌	✅	❌
Manage goals	❌	❌	✅	❌
Manage segments	❌	❌	✅	❌

---

Web Experimentation permissions

These permissions apply only to Web Experimentation.

Permission	⚙️ Admin	🧑‍💻 Technical	📈 Marketing	🚀 Production
Manage widgets	✅	✅	✅	✅
Manage integrations	✅	✅	❌	❌
Manage experiments	❌	❌	✅	✅
Manage personalizations	❌	❌	✅	✅
Launch an experiment	❌	❌	❌	✅
Launch a personalization	❌	❌	❌	✅

---

Feature Experimentation permissions

These permissions apply only to Feature Experimentation.

Permission	⚙️ Admin	🧑‍💻 Technical	📈 Marketing	🚀 Production
View all configurations (environments, flags, variables, variations, goals, and Rollout Planner)	✅	✅	✅	✅
Manage flag configurations (create or delete flags; manage variables, variations, goals, and Rollout Planner)	✅	✅	❌	✅
Manage flag integrations	✅	✅	✅	✅
Toggle flags on/off	✅	❌	❌	✅
Edit environments	✅	❌	❌	❌
Access the feature flag dashboard	❌	❌	✅	❌
Access the Reporting section (Results, Activity Log, and Integrations) of a feature flag	❌	❌	✅	❌

FAQ

Can Kameleoon employees access my account, and how does Kameleoon control that access?

Kameleoon employees can access your account only when a documented operational need requires it, under a least-privilege, role-based access model. Operational needs include service delivery, support, troubleshooting, security operations, and incident response. Access to your account isn’t broadly available within Kameleoon. Only authorized personnel with a documented need can reach it.

This answer covers access by Kameleoon staff. To control which members of your own team can access your account and what each of them can do, see Roles and Manage your users.

Which Kameleoon employees can access your account

Authorized access can include support or service personnel assigned to your account. Kameleoon restricts production-level access to specifically authorized technical personnel. All access to production systems requires multi-factor authentication (MFA), and Kameleoon reviews that access regularly.

What Kameleoon employees can do in your account

Kameleoon employees can’t take unrestricted actions within your account. Role-based permissions, environment segregation, and tenant-level authorization controls constrain all activity. Kameleoon logs all access and administrative actions and makes them auditable.