Coupa Admin role is assigned to designated individuals within organization who support and ensure optimal configurations and data availability for daily business transaction workflows. The role provides access to all of the master data tables and global configurations to enable optimal successful usage for end users according to company policies. As Coupa is a global solutions provider in spend management there are customers with presence in many countries and have their own unique local requirements and processes configured into their system. Admin support structure is often distributed in these locations to allow for optimal timely local user support. The typical structure is that there is a global Administrator in main headquarters where the company operates with other locations supported by local admins with a limited admin access that allows them to manage and support local business processes. These type of users would have a more limited configured Admin role with local data access. The limited role can be built out to give individual permissions to the areas mentioned in the table below. Main system Admin in HQ would be involved in any global updates in configuration and support local admins.
The data is governed via content groups assignment where local admin would share same content group as one assigned to master data. Global system admin would not have content group restrictions. For more on content groups please see our Help Articles area.
|Global Data (managed by Global Sys Admin)||Local Data (managed by local administrators)|
|Company Information (global system settings)||Suppliers|
|Lookups and Lookup Values||Users|
|Units of Measure||Items|
|Security Controls||Buying Policies|
|Custom Fields||Order Lists|
|Home Page / Announcements|
It should be noted that some of the master data would be managed via integrations which helps automate changes and does not require admin manual maintenance. As part of solution design it should be noted what master data points and configurations would be managed between system admins vs. automated integrations. Majority of global configurations are also fairly static once the implementation design is signed off and closed and all locations are successfully rolled out and operating in production. This coupled with automated integrations allows local admins to operate without need for frequent dependency on global system admin in their respective areas.