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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,375
Community Members
 
Community Events
176
Community Groups

Rights and Gate Keeping

I am interested to know who in your organisations has the right to add what to the wiki? How structured are you all in this approach. The organisation I am in has zero rules or guidelines and it's a free for all. The result is a difficulty in finding information. 

So what rules and regulations do you have in your organisations for who can post what , where and when? 

Thanks

2 comments

What I find works best in most places is ownership

For each space, or set of spaces, find/elect a few people who you can make responsible for the spaces.  Make them space admins, and name them somewhere as the area champions/curators/admins/owners

Get them trained in the basics - space permissions (so they can control who can or cannot write in their spaces), how restrictions work, how to easily re-arrange, merge or delete pages.  And give them the authority to tell authors in their spaces to stop doing it wrong.

Like # people like this

I will definitely be having champions/admins etc; that's for sure. Thanks. 

I like Nic's idea of empowering people on your team. One other tool that may help is having a style guide for how each article should look to keep things consistent. Our's covers everything from how to use lists in instructions, grammatical consistency, down to which words should be bolded. 

I am thinking about using the style guide from the company branding. So that our Confluence can take on a look and feel as something in house. At the moment it looks like the internet version 1.0 with very little fluff padding or style which makes it incredibly boring to look at , and therefore difficult to access required information on a page. 

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events