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!


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
Community Members
Community Events
Community Groups

Team Calendars - How to allow events creations while disallow removal of existing Events Types?

Nicolas Casel
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 29, 2022

In Confluence Team Calendars, our users are allowed to create / edit events in a specific Calendar.

However, it means they are also allowed to remove existing 'Events Types':

And if they remove an existing 'Events type', all events related to this 'type' will disappear from the Calendar. But if I set a restriction on the Calendar (only me can add / edit), they will not be allowed to create Events any more ...


Is there an 'intermediate' solution? Based on documentation I get:


I don't think so, but I would like confirmation. Thank you!


1 answer

1 accepted

1 vote
Answer accepted
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 29, 2022

@Nicolas Casel Team calendar permissions are not that granular and work as you have described.  I looked to see if there was an enhancement request for this functionality but did not find one.  I would suggest submitting one here: 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events