Understanding User Roles

As an Administrator on a Socrata-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.

Socrata 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 Socrata user can only have one role per domain. The set of roles are Administrator, Publisher, Editor, Designer, and Viewer.

Socrata 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 to users with or without a role on the domain.
 
Domain roles overrule dataset permissions. For example, an Administrator on a domain can view or edit any dataset on that domain. 
  
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 side-wide analytics  
Manage metadata settings: categories, custom fields        
Create and change SDP templates        
Manage federation between Socrata domains          
View private DataSlate pages        
Manage dataset Routing & Approval          
Moderate comments, views and dataset suggestions        
See data catalog (/browse) list of assets
See "My Assets" and "Shared to Me" tabs on /profile and /admin/assets  
See "All Assets" tab on /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 Public
Datasets                  
Upload & own datasets          
Create a working copy / edit data          
Publish a working copy            
Delete a dataset            
Bypass Routing & Approval Queue                
Views                  
View public, published & approved views / datasets
View an unpublished, private, or rejected pending view    
Create views on datasets
(maps, charts, filters, etc)
Save views on datasets  
Modify a view            
Create a Data Lens view on a dataset        
Save As a new Data Lens            
Modify a Data Lens            
Transfer Ownership of a view to another user              
Make a view Public or Private            
Share a view with another user          
Bypass View Moderation Queue              

 

For information on how to manage the role assigned to users, see the knowledge base article "How do I manage user accounts and roles on my data site?".

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

Comments

0 comments

Please sign in to leave a comment.