Skip to main content


Granicus Insights

Roles and Permissions Quickguide

Core roles and permissions



(User Type)



(What can I do?)


Anonymous User: 


General site visitors that are not logged in.

This user type has no profile information, hence it’s anonymous.

  • View and search content on public website.

Granicus Open Data recognizes this user type to let it see and search content, but doesn’t let the user add comments.

Authenticated User:


These users are logged on and have profile information that can be verified (and authenticated).

This type has the lowest level of permissions; all users with login credentials have this role. This user type is a general site visitor but he or she has created an account.

  • Have a profile and add/edit that profile.

  • Can leave comments on the data catalogue.

Granicus Open Data can verify account information with a created profile so that the user is able to take limited actions and manage profile details.

Content Creator:


Content Creators are focused simply on adding resources to the data catalogue under direction of a supervisor.

At this level, the role must be assigned by a higher role; this role has access to the production side of the site. This will be someone working in your organization who helps by adding to the data catalogue but doesn’t need to worry about the whole site.

  • Create most content types and edit own content.

  • View own content and revision history of all published content.

  • Add and view files to site library.

This level of access takes users into the production side of the site, but gives little freedom to move outside of creating and adding certain content types. Limiting this role is critical for avoiding inadvertent damage to site content.



This will typically be a person handling the content on a frequent basis. Someone in your organization with expertise on the subject-matter that is expansive as well as in-depth.

An editor role is similar to a content creator role because the focus is content, however an editor will deal with multiple content authors and have the ability to manage and edit. An editor is responsible for managing content from a strategic perspective.

  • Assign roles to lower-level users.

  • View, edit, delete most content types and manage versions of content.  


  • Access and manage the Datastore

The editor largely handles the quality and timeliness of the content that appears on the site. This role is able to make changes to content and where it appears, but it doesn’t go further into admin functions.

Site Manager:


The highest-level for non-technical users. A site manager is mostly concerned with admin functions of the site. Typically this will fall to someone in a supervisory role.

The site manager takes a high-level view of the site, its content, and the users on the site. This person maintains the site and assigns roles and permissions to new users but doesn’t deal with the technical backend.

  • Create, edit, delete all content types created by any user.

  • Change the types of content that lower-access roles can create.

  • Assigns roles to all user levels, but cannot create new roles/perms.

  • Create and manage groups.

The site manager handles the admin part of the site. This role keeps the production side of the site in good order so that editors and contributors can focus on what site visitors see on the website. This is still largely a non-technical role.



The administrator role holds every permission, and it requires high technical competency. This role has the ability to cause serious damage, so it’s generally reserved for a single web professional.

The administrator handles the overall structure of the website for lower-access roles to plug content into and make changes as needed. Admins hold the highest level of all roles and permissions.

  • Enable/disable Granicus Open Data modules and features.

  • Change the appearance of the site with views and themes.


  • Create and edit  user roles and permissions.  

Administrators are the middle piece between users using a site daily and the core functions built in the technical backend. Based on an organization’s requirements the administrator can adapt the site to meet daily needs of users.



  • Was this article helpful?