Splunk® Success Framework

Splunk Success Framework Handbook

Download manual as PDF

Download topic as PDF

Community portal best practices for a Splunk deployment

A Splunk community portal is a great way to keep your community engaged and informed. A community portal serves several purposes:

  • Exchange ideas and offer support
  • Identify common goals and interests
  • Build a thriving and growing Splunk community
  • Provide space for open collaboration


  • Knowledge manager
  • Program manager
  • Project manager
  • User community

For more about these roles, see Roles best practices.

Guidelines for establishing a community portal

A community portal is a shared resource where users can get an overview of activities the Splunk community is engaged in, and resources they need to be successful with Splunk. There is no prescribed layout for a community portal. Design the community portal in the way that works best for your users on a platform they use regularly. Your community portal can feature Splunk resources, updates, announcements, key processes, user questions and answers, and contact information for submitting requests or feedback.

Start by identifying the needs of your users, then design and create a draft of your portal:

Identify the needs of your users

Who are my stakeholders?
Identify the Splunk user roles in your environment. Refer to the Staffing best practices and Roles best practices.
What kind of content do they need to see?
Consider what they need to know. For example, an executive sponsor and program manager may want to see a program status, and an expert user or knowledge manager may want to see discussions about how to model data from certain data sources.
What collaboration medium or application is best?
Platforms used by thriving Splunk communities include Jive Interactive Intranet, Microsoft Sharepoint, and Confluence. Some organizations start out with a central file repository before choosing a platform.

Splunk resources section

Your community portal should include a Splunk resources section with user roles and relevant content for each user type. The example below shows a matrix of relevant content sorted by user role.


Recommended actions

  1. Once your portal is designed, try it out on some users to make sure your portal is meeting their needs.
  2. Assign a team to add fresh content and monitor any questions posted to the forum.
  3. Create a maintenance schedule for your community portal.
  4. For inspiration, see the Splunk Community.
Communication best practices for a Splunk deployment
Back up and restore best practices for a Splunk deployment

This documentation applies to the following versions of Splunk® Success Framework: ssf

Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters