In Optimizely X Web, users are called collaborators. Collaborators have different levels of permissions. Use the collaborator roles to manage user-based permissions and access to your Optimizely X Web projects. These roles are especially useful when there are multiple people working on the same project or campaign.

The collaborator roles are:

• Administrators have full access to all projects and account billing information. They can also add and remove other administrators. If you make someone an administrator, they are one on every project. If you change an administrator to any other role, they lose all privileges on other projects.

• Project owners can create, edit, publish, start, and pause experiments and campaigns. A project can have more than one project owner. Project owners can also create new projects and invite editors and viewers to the projects they own.

• Publishers can create, edit, publish, pause, and unpause experiments and campaigns; view results; and create and modify audiences, metrics, and pages. A publisher has full power to create, start, and stop experiments, but cannot change the configuration settings for the project, e.g. the snippet. 

• Restricted publishers have a limited version of the publisher role. A restricted publisher can only use pre-made extensions to create experiments. They cannot use the Visual Editor or Code Editor. Otherwise, they have the same abilities as a publisher. 

• Editors can create pages and events; create and modify audiences; and create and edit non-running campaigns. Editors can create experiments, but can't start them. They can also view results.

• Restricted editors have a limited version of the editor role. A restricted editor can only use pre-made extensions, and cannot use the Visual Editor or code editor. Otherwise, they have the same abilities as an editor.

• Viewers can preview campaigns and view results.

Most of the collaborator roles in Optimizely are project-specific, meaning that you can have different collaborator statuses across different projects. However, this also means that collaborator roles need to be managed per project, so if you want to change someone's Editor status to a Viewer in multiple projects, this needs to be done for every project separately.

One exception to the above rule is the Administrator role. This role gives complete access over the entire account and, as such, all projects linked to that account. If you make a collaborator an Administrator in an account, this is applicable across all projects. Similarly, if you downgrade the status of an existing Administrator, this applies to all projects.