Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Assets Permissions Question

Joshua Bennett November 15, 2024

 

In Jira Assets, if I set permissions on the Schema level, but also have permissions set on an object type within that Schema, have I effectively 'disabled inheritance' (in Windows speak) on that object type so only the permissions set on the object level apply? 

Then conversely, if I never set permissions on the object type level but only at Schema level, do the permissions set at Schema level apply to all objects? 

1 answer

1 accepted

4 votes
Answer accepted
Mikael Sandberg
Community Champion
November 15, 2024

Permissions on the object type level can override the permissions set on the object schema level. Have a look at this KB, there is a good example under the Object type permissions vs object schema permissions section.

And if you do not set permissions on the object type level, the permissions on the object schema level will be inherited.

Joshua Bennett November 15, 2024

Hi  -thank you - that was very much my suspicion and KB described it well. 

 

So I'm now thinking that, wherever possible, Schema level is the way forward all the way, because permissions are overridden not accrued when set at object type level. Would you agree?

 

I kind of think our org has got itself in a bit of a mess by setting permissions on the object type level, possibly they didn't realise that this wasn't necessary for each object type. 

Mikael Sandberg
Community Champion
November 15, 2024

Yes, I think setting the permissions on the object schema makes it easier to maintain. I can see where it can be used on the object type level, for instance if you information in that that should only be visible to a subset of users, but I recommend to stay away from it if possible.

Like # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events