You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have one specific object type in our object schema that we do not want any users besides Admins to be able to create new objects in. For that object type (Class), I have set up Roles:
However, when I had a non-admin go in to validate that they could no longer create new objects on that object type, they were still able to. Any ideas as to why they still have that ability? Thanks!
My thought is that the Object Schema Permissions take precedence over the Object Type Permissions.
It's probably worth trying the configuration to confirm:
This should confirm or deny my theory that the Object Schema permissions take precedence over the Object Type Permissions.
Suzi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.