All Collections
Account Management
Team Collaboration
How can I manage my team's roles and permissions?
How can I manage my team's roles and permissions?

Control who publishes Chameleon Experiences or changes account-wide settings with specific Roles

Chameleon Team avatar
Written by Chameleon Team
Updated over a week ago

You can invite your whole team to contribute to your in-app efforts and leverage the different Experiences you can build with Chameleon. And empower each teammate with access to the right configurations to ensure efficiency, speed, and control in delivering a pleasant user experience.

With our Roles functionality, you can allow teammates to contribute in a way that does not tamper with your existing efforts but amplifies your guidance.


Availability & Usage

πŸ” Startup: Admin

πŸ” Growth: Admin & Viewer

πŸ” Enterprise: Admin, Teammate, Viewer

πŸ“© Contact: to discuss your plan


What Roles are available in Chameleon?

When the Roles functionality is enabled, you can pick between 3 major Roles and set different permissions for each teammate on your account:

  • Admin

  • Teammate

    • Creator

    • Designer

    • Publisher

    • Engineer

  • Viewer

β„Ή "Viewers" do not consume seats on your account no matter the plan.

Admin Role

"Admins" have full access to control any setting, configuration, or create and publish Experiences. These are some of the permissions that "Admins" have:

Teammate Roles

These Roles enable you to ensure that all critical configurations are in the right hands and every teammate can efficiently contribute to your product's success. Here's a brief description of each, or check out the table with detailed permissions across Chameleon.

Creator

✨ "Creators" are those who power your in-app guidance and ensure all user needs are addressed with the right Experience.

All "Creators" on your account can create Tours, Tooltips, Microsurveys, Launchers, and add content to your HelpBar. They can also delete drafts and archive Experiences on your account, as well as create Segments.

To drive engagement or enhance your Segments, they can also:

Publisher

✨ "Publishers" are your final advisors who check that all configurations deliver maximum engagement with minimum disruption for users.

"Publishers" can create and publish any Tour, Tooltip, Microsurvey, or Launcher, as well as add content to your HelpBar and publish any latest changes (e.g. updated Trigger).

"Publishers" can access more configurations that ensure a pleasant user experience:

Designer

✨ "Designers" ensure any Experience you create looks natively integrated into your interface no matter the style evolution of brand.

"Designers" on your account can set your Brand Basics and Detailed Styling. They can also tweak the look of Experiences with custom CSS, and create different Templates for your team to use.

πŸ‘‰ They can also leverage our Figma Components file to establish your in-app style before updating your Styling in Chameleon.

Engineer

✨ "Engineers" cover your Chameleon installation and ensure you're all set to create Experiences and successfully receive data in your account.

"Engineers" can access the installation methods and add the Chameleon code to your app. They can also use our API to manage your data, generate API Tokens, access Webhooks, or configure your integrations and Environments.

Viewer Role

✨ "Viewers" can include anyone from your data analyst to a new teammate exploring your use of Chameleon for a new initiative.

"Viewers" in Chameleon can access your Dashboard and all Experiences, see different settings, configurations, or integrations you enabled, but they can not edit or modify anything in your account.

They can review Tags, Alerts, or Rate limits, as well as filter through data, or try out the different Segment filters available for creating an audience in Chameleon.

Viewers can also:

  • Download CSVs (Experience data, YAML translation files)

  • Summarize Microsurvey responses to review

  • Export Segments to review user data


Permissions across Chameleon

See the different permissions for each Role detailed in the table below πŸ‘‡

C = Create

R = Read

U = Update

D = Delete

P = Publish

Page/

Action

Admin

Designer

Engineer

Publisher

Creator

Viewer

Get Started - Install

CRUD

R

R

R

R

R

API Access

-

-

CRUD

-

-

-

API - Manage Roles

RU

-

-

-

-

-

API - Manage Data

(Update / Delete Companies, Profiles, Deliveries, Environments)

CRUD

-

CRUD

-

-

-

Integrations

CRUD

R

CRUD

CRUD

R

R

API Tokens

CRUD

R

CRUD

R

R

R

Webhooks

CRUD

R

CRUD

R

R

R

Settings - Account

CRUD

R

R

R

R

R

Settings - Domains

CRUDP

R

CRUDP

R

R

R

Settings - Rights

CRUD

R

CRUD

R

R

R

Settings - Billing

CRUD

R

R

R

R

R

Settings - Team (Admins can invite any role. Publishers can invite Creators. All other invites are assigned the Viewer role)

CRUD

R

R

CR

R

R

Style Editor

CRUD

CRUD

R

R

R

R

Custom CSS

CRUD

CRUD

R

R

R

R

Templates

CRUD

CRUD

R

R

R

R

Tours

(D*-- can delete any draft and can archive anything)

CRUDP

CRUDP

R

CRUDP

CRU+D*

R

Tooltips

(D*-- can delete any draft and can archive anything)

CRUDP

CRUDP

R

CRUDP

CRU+D*

R

Microsurvey (D*-- can delete any draft and can archive anything)

CRUDP

CRUDP

R

CRUDP

CRU+D*

R

Launchers

(D*-- can delete any draft and can archive anything)

CRUDP

CRUDP

R

CRUDP

CRU+D*

R

HelpBar

CRUDP

R

R

CRUDP

CRUD

R

Segments
​(D*-- can delete the ones you create (as long as they are not attached to live Experiences)

CRUDP

R

R

CRUDP

CRU+D*

R

Rate Limiting

CRUDP

R

R

CRUDP

R

R

Alerts

CRUD

R

R

CRUD

CRUD

R

Data Management - User Properties

(Also applies to β€œSend user data” in button Action)

CRU

R

CRU

R

R

R

Data Management - Company Properties

CRU

R

CRU

R

R

R

Data Management - User Events

RU

R

RU

R

R

R

Data Management - Tags

CRUD

R

R

CRUD

CRUD

R

Data Management - Imports

CRU

R

R

CRU

CRU

R

Data Management - Localization

CRUD

R

R

CRUD

CRUD

R

Builder

(Viewer: cannot β€œEdit” or open the Builder on new domains. All non-Viewers can "Edit" in the Builder and open on new domains.

inherited

inherited

inherited

inherited

inherited

R


Member permissions (Legacy)

Growth accounts that previously enabled the Roles functionality and did not upgrade to our new Roles and permissions, will have limited access. The 3 Roles will be available with the following Teammates Roles:

  • Admin

  • Teammate (Engineer, Designer, Creator)

  • Viewer

πŸ”’ To change the Roles on your account contact us to upgrade your plan.

"Teammates" on your account can create any Experience as normal and access other Chameleon functionality (such as Styling or integrations), but they cannot publish Experiences and require Admins to do so.

Did this answer your question?