User roles available in District Engage
When a user is created, a role needs to be assigned. A single user can have multiple roles assigned, both at the system level and within teams. Click here for more information on user creation.
Users can be assigned roles at both the system level and within specific teams. To learn more about how teams work and team-specific permissions, see our guide on Understanding and Managing Teams.
The following system roles are available to assign to an internal user in District Engage:
Role | Detail |
Administrator | This role has the highest level of permissions, and can perform all actions on the platform. An Administrator can:
This role can perform all actions of the following roles: Team Lead, Project Manager, Publisher, Reviewer, Engagement Officer, and Public Moderator |
Team Lead | A Team Lead can:
Within their assigned team(s), a Team Lead can perform all actions of: Project Manager, Publisher, Reviewer, Engagement Officer, and Public Moderator |
Project Manager | A Project Manager can:
A Project Manager can perform all actions of the following roles: Publisher, Reviewer, Engagement Officer, and Public Moderator. When assigned to a team, these permissions apply only to that team's projects. |
Publisher | A Publisher can:
|
Reviewer | A Reviewer can approve or reject:
|
Engagement Officer | An Engagement Officer can:
|
Authenticated | This role applies to public users who have logged into your website. |
Internal user roles hierarchy
Note: Only administrators can create new roles. The diagram below displays the hierarchical structure of internal user roles, not role creation permissions. Each role listed at the top of the diagram possesses its own set of permissions, as well as all the permissions of the roles listed beneath it. When roles are assigned within teams, this hierarchy applies only to that team's projects.
When a user is assigned a role within a team, their permissions are limited to that team's projects. For example, a Publisher in Team A can only publish content for Team A's projects. Learn more about team-based permissions in our Teams Guide.