Roles-based feature access

Different roles of the Persona-based UI have different levels of interface access.

Home page role privileges
Sub-feature Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Home ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Data explorer feature role privileges
Sub-feature Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Item Explorer ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Category Explorer ✓ ✓ ✓ ✓ ✓
Search feature role privileges
Sub-feature Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Item Search ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Digital Assets ✓ ✓ ✓ ✓ ✓
Category Search ✓ ✓ ✓ ✓ ✓
Transactions ✓
Design manager feature role privileges
Sub-feature Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Catalogs ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Collaboration areas ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Hierarchies ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Lookups ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Workflows ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Job manager feature role privileges
Sub-feature Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Jobs ✓ ✓ ✓ ✓ ✓ ✓ ✓
Data model manager feature role privileges

Sub-feature

 Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Spec console ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Attribute collection ✓ ✓ ✓
Rules engine ✓ ✓ ✓
Data management feature role privileges
Sub-feature Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Digital assets ✓ ✓ ✓ ✓
File explorer ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Dashboards feature role privileges
Sub-feature Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Audit history ✓ ✓ ✓ ✓
DAM summary ✓ ✓ ✓ ✓ ✓
Data sanity ✓ ✓ ✓
Jobs summary ✓ ✓ ✓ ✓ ✓ ✓ ✓
User summary ✓ ✓ ✓
Vendor summary ✓ ✓ ✓ ✓
Worklist summary ✓ ✓ ✓ ✓ ✓
Custom tools feature role privileges
Sub-feature Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Custom tools ✓ ✓ ✓ ✓ ✓ ✓ ✓
Global Data Synchronization feature role privileges
Sub-feature Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Manage Items ✓
Synchronization Reports ✓
Utilities feature role privileges
Sub-feature Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Locks (DB) ✓   ✓          
Log search ✓           ✓          
Variant mapping ✓ ✓ ✓ ✓
Settings feature role privileges
Sub-feature Admin Basic Catalog Manager Category Manager Content Editor Digital Asset Manager Full Admin GDS Supply Editor Merchandise Manager Service Account Solution Developer Vendor
Personalization Settings ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
FTS Settings ✓ ✓ ✓
DAM Settings ✓ ✓ ✓ ✓ ✓ ✓
Change Password ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Chatbot Settings ✓ ✓ ✓
Theme ✓ ✓ ✓
Polling Time ✓ ✓ ✓
Error Panel Settings ✓ ✓ ✓
Company Setup ✓     ✓     ✓       ✓  
Data Survivorship ✓           ✓       ✓  
If you create a custom role, through the Data model manager > Security > Role Console in the Admin UI:
  • You can add your role in the mdmce-roles.json file and apply the appropriate default role permissions.
    Important: You should not remove the "name": "Settings" content from the file because it is required to log in to Persona-based UI.
    OR
  • You can create a role and apply appropriate parent role permissions for each user.
    Example
    You create a custom role, for example "XYZ_editor" based on the Content Editor role and for each user, apply the default Content Editor permissions to the XYZ_editor role.