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.
Hello,
configuring-roles-and-permissions
According to documentation, we can configure object-type-level permissions but here is what I am experiencing:
If a user has an Object Schema Users role, she can view every object type and object under the given Schema. If user does not have any schema-level role but has a Object Type Users role, she is unable to view the schema, therefore cannot access the object type.
So, what is the purpose of Object Type Users role field in this case? What am I missing?
I want a user to be able to access a particular object type. Would appreciate any suggestions setting this up.
Thank you.
I found this post as I had exactly the same question.
Playing with it a little since the docs aren't clear, it seems that giving access at the object-type level gives the user/group access to edit the objects in that type, and the types under it in the hierarch (even though if you open a child type you don't see the group listed there, you can edit objects in children types)
so, changing this makes the buttons for edit and comment appear/dissappear for objects in that type
Not what I was hoping would be the case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.