Setting roles and responsibilities
A Splunk implementation team is made up of roles with different strengths and skills with Splunk software and within your general business. These roles reflect the business skills needed to fulfill the role's duties, and do not necessarily map directly to the Splunk platform default user roles - for example, one person on your Splunk team can fulfill more than one role.
Roles and responsibilities are a good way to manage an incentive-based access model to encourage your user community to build and grow their Splunk software skills.
Splunk roles and responsibilities
Here are common roles in a Splunk implementation, their general focus, and the recommended minimum level of Splunk education required for that role.
Splunk role and responsibilities | Required skills | Recommended education requirements |
---|---|---|
Architect |
||
|
|
Learning Path: Certification: |
Developer |
||
|
|
Learning Path: Certification: |
Engineer |
||
|
|
Learning Path: Courses for Splunk Administrators Certification: |
Executive sponsor |
||
|
|
Learning Path: Certification: |
Search expert |
||
|
|
Learning Path: Certification: |
Knowledge manager |
||
|
|
Learning Path: Courses for Knowledge Managers Certification: |
Program manager |
||
|
|
Learning Path: Certification: |
Project manager |
||
|
|
Learning Path: Certification: |
User community |
||
|
|
Learning Path: Certification: |
More resources
- For information about how to set up roles and capabilities in Splunk Enterprise, see Define roles on the Splunk platform with capabilities in the Securing Splunk Enterprise manual.
- For best practices about how to manage roles, access to data, and access to product features in a more modular and scalable way, see the topic Managing data based on role.
- For a staffing model template, see Staffing a Splunk deployment.
- For the responsibility assignment matrix, see Assigning Responsibilities