Different roles are available to grant different levels of permissions to MadKudu users in Copilot, App and Data Studio.
User roles
| Admin | Architect | User | Sales User |
User Management | ✍️ can edit | ❌ no access | ❌ no access | ❌ no access |
Integrations Configuration | ✍️ can edit | 👀 can view | 👀 can view | ❌ no access |
Copilot | ✍️ can edit Can create Org and User level playbooks Can edit Account & Contact Intelligence layouts | ✍️ can edit | ❌ no access | 👀 can view Can create private playbooks, edit book of account |
Scoring Configuration | ✍️ can edit | ✍️ can edit | 👀 can view (only Live models) | ❌ no access |
Admin (all permissions)
Recommended to assign the Admin role to the users who can manage users, integrations, copilot settings, and edit the scoring configurations. This would usually be a RevOps, MOps, SalesOps...
Architect
Recommended to assign the Architect role only to the users in your company who need to edit the scoring in the Data Studio. This would usually be Marketing Ops or Data Scientists.
User
Recommended to assign the User for people who don't need to manage users nor the configuration of the platform but who would need to understand the configuration of the scoring and consult the Predictions and Insights reports. Example: Growth, Marketing, DemandGen, Data....
Sales User
Recommended to assign the Sales user role for any Sales reps (SDR, BDR, AE, AM....) and their leadership to use Copilot (in Salesforce or Chrome extension)
Permissions
User Management
adding/deleting users
changing roles
configuring the Authentication mode (Single Sign-On) and auto-join
Integrations Configuration
updating the connection to the systems connected to MadKudu, such as your Salesforce, Marketo, Segment, etc.
checking the API usage
Copilot
accessing Playbooks, Explore, Account & Contact Intelligence
Scoring Configuration
editing mappings in App
editing Computations, aggregations, and models in the Data Studio