Building a Splunk Community

Because that’s what you are doing! You are building your own Splunk Community. So, how do you want it to look? What topics and content do you want your community members to rally around? Who is on your team?

Each Splunk User Group Chapter is comprised of a leader or leaders. It is up to those leaders to choose who will be on that team. You are able to add as many helpers as you’d like.

So, create your team and Let’s Grow! Here are the instructions for your helpers to create accounts in the dashboard.

Have them create an account

First things first, create an account:

Head to the login page of the dashboard

Click “Create Account”

Fill in the information

Click “Sign Up”

Next, set up your profile:

Click on your photo avatar in the top right corner

Click “Profile”

Click “Edit Profile” in the top right

Fill out your bio & upload a photo; you are free to limit which social channels to whatever you are comfortable sharing.

Add them to your team

Once their application has been approved, one of our team members will give them admin permissions to both

Community.splunk.com⁠

and

Usergroups.splunk.com⁠

Invite them into the Splunk Community Slack

If they aren’t in the community already, have your new team member join the

Splunk Community Slack Workspace⁠

We ask for them to fill out the application form to join, so we can collect some information about them for our system.

Introduce them to the Splunk Community!

Make sure to introduce your new team mate in the #splunk-usergroups Slack channel as well as the private leadership channel that you swill be added to! These channels are private, but you are able to tag them in a post and invite them to join

You are managing a local Splunk community, and you’re often the first point of entry for a lot of people into this community! Your chapter members look to you for resources and news about Splunk User Groups!

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.