Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Confluence Content Management: Part 2

Forming an Advisory Board

If you don’t already have one, create an advisory board to establish standards, support the admins, and advocate for users.

Ideally, the board includes the following types of contributors:

  • An end user who understands how other users leverage the software.

    • This could be a technical or a non-technical user.

  • An application administrator who understands the software’s structure and capabilities.

  • A project manager, business analyst, or strategist who can help craft and implement effective processes.

  • A VP, application owner, or similar leader who's responsible for the application and its data.

  • And a wildcard member who can keep the group focused, communicate with other groups, and provide additional skills or expertise as needed.

The worst type of person to have on your board is someone with a narrow focus. Someone only interested in their specific problem won’t make decisions that benefit the software and user base as a whole. Be prepared to replace any board member who doesn't bring value to the team or negatively impacts its mission.

Also, not every member of the advisory board needs application administrative access! This access level should be carefully limited to a small group of people who genuinely care about the application and the work it supports.

Part 3: Making Content Decisions



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events