Unable to change permissions/scope for Add-on user

[Dritan Xhabija]

Hello,

I keep getting 403 when trying to fetch the currently logged user via ACE add-on I've added to my cloud instance so I can verify whether user is admin (and other queries pertaining to the user so I can show appropriate menu items based on permission levels).

I'm torn up because according to your documentation, you allow add-ons to have a scope https://confluence.atlassian.com/upm/add-on-scopes-445186491.html YET I'm denied to make such a change "because customers are not able to modify system users in any way." -- https://jira.atlassian.com/browse/ID-6572?_ga=2.126645133.161444563.1529087175-323932314.1487801975

I don't understand. Am I or am I not allowed to give a different scope to my add-on (user) so I don't get 403s? What good is that scope documentation listed above?

Thanks,

Dritan

[Dritan Xhabija · Accepted solution]

It's great that all the human-readable scopes are defined here https://confluence.atlassian.com/upm/add-on-scopes-445186491.html?_ga=2.169138977.161444563.1529087175-323932314.1487801975
 
but what good are those if it doesn't explain where to use them? at the very least mention "atlassian-connect.json" -- otherwise, WHERE ELSE can these scopes actually be used? Ideally this link would have made all the difference. to https://developer.atlassian.com/cloud/jira/platform/scopes/
 
That last URL explains where to use scopes (and not just *what* they are) and it's not the same as changing permission of an existing (system) user. And it makes perfect sense why no customer is allowed to make changes to system users (whatsoever) since each addon defines its own permissions in atlassian-connect.json. 
 
I hope this helps anyone else who also finds Atlassian documentation disconnected. You could easily write a script that could link concepts/pages together -- cohesion in these documentation needs a lot of work.