User roles | Civio Engage Knowledge Base [ ![Civio Knowledge Base](/civio-light.svg) ](https://nginx.deploy-lagoon-production.engage-vic-docs.dh1.amazee.io) [Articles](/articles) [Home](/) [Knowledge base](/articles) [👤 User configuration ](/articles?category=3) User roles ========== Updated 2 months ago Search Go System vs team roles ==================== **System roles** ---------------- When adding a new user, a system role needs to be selected for this user. ![image - 2024-03-11T134559.230.png](/storage/articles/9493366877839.png) A system role is a role that allows permissions to *every section of Civio Engage*, and is not specific to a team or project, such as permissions to access the dashboard. The following system roles are available in Civio Engage: - Public user - Internal user - Admin - Superadmin Any system role other than public user is considered an internal user role. *Internal user* is the default role given to any new user. Additional system roles can be assigned to users or replace this default role. For example only Superadmins will be able to manage user roles and permissions. The majority of users will be granted the system role *Internal user* and be granted team/project specific permissions when assigned a team role. Team roles (Department teams, campaign teams, projects) ------------------------------------------------------- Team roles allow *permissions in a specific context of a department team, campaign team, or project*. When a new user is created, this user can be assigned a team role within a specific department team, campaign team or a project. Within the context of a team or project, either one of the following team roles can be assigned to a user: - Engagement manager - Project manager - Author - Reviewer - Moderator Department teams vs campaign teams ---------------------------------- When creating a project, you need to assign this project to a team (*department or campaign team*), as every project within Civio Engage is owned by a team. A department team can own multiple projects. A project can also be part of one or more campaign teams. A campaign team groups projects across different teams. For example project A can be part of department team A, project B is part of department team B. But both project A and B can also be part of campaign team C. Assigning a project to a campaign team is only optional, while assigning a project team owner is a requirement for creating a project. Managing roles -------------- Civio Engage roles and permissions can be managed by Superadmins only. ![046e8e3a-98f6-4d91-992d-6e8cf530d9df (1).png](/storage/articles/9493366878351.png) To edit the roles and permissions: 1. Log in via your Civio Engage website. 2. In the top right of your screen, click your **username**, then **Dashboard**. 3. In the top-level menu, click **People**. This takes you to the **People Overview** screen. 4. In the left-hand menu, click **Roles**. This gives you a list overview of all system and team roles set up in Civio Engage. 5. Select which role you'd like to edit from the list. 6. Click on the **ellipsis button** to show more options for a role. Click **Edit**. 7. You will be able to edit the role name, role type (System role or Team role), and update the permissions according to different permission groups. 8. When you're finished, click **Save**. Permission groups ----------------- User permissions have been structured into permission groups. ![image - 2024-03-11T133107.879.png](/storage/articles/9493350465167.png) Most of these permission groups are fairly self-explanatory and clearly described on the role page. Other permission groups might need further clarification: **Project page content**Permissions in relation to content that can be created for specific projects. For example the creation of an event or a project timeline stage for a project.**Public participation**Permissions for **participation tools** **submissions** such as survey submissions, ideas, questions, as well as **comments,** are managed in the **Public participation** permission group. This includes both public user permissions to submit content on the frontend and internal user permissions to manage submissions.**Project consultation tools**Permissions for creating and managing participation tools are managed in the **Project consultation tools** permission group. For example, the permission to create a new survey or update an existing idea topic.**Project sub pages**Permissions in relation to the creation and editing of pages for specific projects.Permission terminology ---------------------- Clarification of terminology used in the Permissions section: '**View any**' page, '**View any**' comment, etc'View any' permission allows you to see full list of pages/projects/comments/etc within the context of your permissions. For system roles these permissions apply to all sections of Civio Engage, while for team roles this depends on the specific departments/campaigns/projects the user is assigned to.**'View any' project**Be careful with assigning the permission field 'View any project' to a system role user, as this user will be able to access all projects within Civio Engage. When users are assigned to a team they can view any project within this team, regardless of this permission granted or not.**(when not project published) vs (when project published)**The same role may have different permissions on content, depending on the project published state. For instance, Project managers may only be able to publish new **project meetings** when projects have already been published**View non published projects**To have the permission to see non published projects, the 'View non published projects' permission within the 'Projects' permission group should be ticked.**Survey submission**With the public participation permission group, 'survey submission' related permission items allow **permission to all participation tool submissions**, not only to survey submissions. E.g. when ticking 'view survey submission', the user will also be able to see question/poll/survey map submissions. [ Back to articles ](/articles) Table of contents ----------------- © 2026 [Civio](https://civ.io)