1. Data & Insights Client Center
  2. Site Administration
  3. User Management and Authentication

Understanding User Roles

Avatar
Andrew
Last Updated:
Follow

As an Administrator on a Data & Insights-powered data portal, you can assign a number of special roles to other users. This will allow you to delegate tasks on your site and enable other users to create and manage datasets.

For Gateway-related permissions, please refer to this article.
For Perspectives (stories) related permissions, see Understanding And Managing Perspectives User Roles.

Data & Insights users can have roles on a domain. A role defines the types of actions that someone can conduct for all datasets and assets on a domain and the configuration of the domain itself. Examples of these actions include importing data, adding features, or managing users. A Data & Insights user can only have one role per domain. The set of roles are Administrator, Publisher, Editor, Designer, and Viewer.

Data & Insights users can also be assigned permissions for individual datasets. Permissions define the types of actions available to a user for each specific dataset. Examples include editing, viewing and publishing that dataset. Permissions available at the dataset level are Owner, Contributor, and Viewer. These permissions can be granted only to users with a Data & Insights account, but they do not need to have a role on the domain.
 
The rights associated with domain roles and asset roles are cumulative. For example, an Administrator on a domain can view or edit any dataset on that domain, regardless of any less-privileged asset-level role that may be assigned to them (e.g. Contributor).
  
Creating visualizations (filtered views, maps, and charts) from existing public datasets on a domain does not require any role or special permissions. These tools can be accessed by any public visitor without the need for a role and without the need to sign in.
 

Domain-level actions

Domain-level actions are affected by a user's role. The following matrix shows the capabilities at each level:

 Domain-Level Actions Admin Publisher Editor Designer Viewer Public
Add, edit and delete user accounts •          
Manage homepage content, including story banner and featured datasets • •   •    
View site-wide analytics •          
Manage metadata settings: categories, custom fields •     •    
Create and change SDP templates •     •    
Manage federation between Data & Insights domains •          
View private DataSlate pages • •        
Manage Approvals •          
Moderate comments, views and dataset suggestions • •        
See open data catalog (/browse) list of assets • • • • • •
Hide/Show assets on open data catalog • •        
Discover assets which they own, assets which have been directly shared to them, and assets released to the public (via /admin/assets) • • • • •  
Discover ALL assets - public and private - across the site (via /admin/assets) • •        


View-level actions

View-level actions are affected by a user's role and any permissions on the dataset or the view. The following matrix shows the capabilities at each level: 

  DOMAIN ROLES DATASET ROLES PUBLIC*
  Admin Publisher Editor Designer Viewer Owner** Contrib. Viewer Unroled Anon.
Datasets                    
Upload & own datasets • • • •            
Create a draft / edit dataset draft • •       • •      
Publish a dataset draft • •       •        
Delete a dataset • •       •        
Enroll a dataset in archival •                  
Views                    
View public, published & approved views / datasets • • • • • • • • • •
Add / Edit filters on a view / dataset • •  •  •  •  •  •  •  •  • 
View an unpublished, private, or rejected pending view • •   • • • • •    
Create and publish derived views (maps, charts, filters, etc) • • • • • • • • •  
Save changes to existing derived views • • • • • • • •    
Modify a view • •       •        
Transfer Ownership of a view to another user •                  
Make a view Public or Private • •       •        
Share a view with another user • •       • •      

 *NOTE: Anonymous users are those that are interacting with data without logging into the platform. Whereas unroled is users who are logged in but without a domain role.*

**A co-owner on an Open Data domain is equivalent to a collaborator on an Enterprise Data domain.**

For information on how to manage the role assigned to users, see the knowledge base article: Manage user accounts and assign roles

Was this article helpful?
4 out of 5 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.

Articles in this section