-
Suggestion
-
Resolution: Unresolved
-
None
-
5
-
36
-
Currently, the apps/add-ons system users are added to the space permissions and granted all the permissions automatically to function correctly.
However, since they are added as space administrators, it crowds out the administrator's space list to see who is a user admin of the space(s), causing some confusion and trouble finding it if there are too many add-ons with admin space permissions.
The suggestion is to improve it to provide a better way to manage it, like in the global settings or if managed by space, to not show the system users such as the add-ons as space admins.
- is related to
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
- Gathering Interest
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFCLOUD-73496] Improve manage app permissions to spaces
jhonda@atlassian.com could you change the Summary to "Ability to Hide Marketplace Apps in Space Users"? We have a major client moving to cloud and this is coming up in admin testing. Every space shows 20+ users for Apps and it definitely makes it hard to see real users. Even a filter would be nice. Of course most user permissions should be via groups but we're all bad space admins 
there are multiple problems I see with the current implemenation:
- it is not obvious that they are app users, how to identify them?
- there names do not relate them to any app, so you never know from what app comes what user
- it is unclear what permissions they need and for what exact purpose
- it is furthermore a data security issue that must be examined in our company as they access data and probably do some processing with it
- you are not informed about there is an app user coming along with an app, it shouldn't just be documented on a page, that no one knows about in order to look it up -> the app should inform actively, e.g. via a pop-up window about it and what it does on installation
- I don't get why in every application this handling is implemented differently:
- in Jira you have an addon group that you grant privilege, e.g. global permissions
- in Confluence Atlassian goes another way
-> I can't see any synergy beetween the tools, no wonder bugfixes are implemented so slowly, if any...
Gliffy customers also confused with this space permissions for apps. Voting up.
+1 for this feature. Literally nobody in our organization is able to find a real admin of a space on the space details page, because of the crowd of system user admins.
Please seperate system user admins from real user admins and only show the real ones on the space details page.
We are facing the same interrogations from our users. There is currently more than 10 "system users" and the end users do not always understand their purpose. Worse: they can remove them without asking.
Additionally, if most of the "system users" are using informative names (linked to the app name/vendor), some of them are very fuzzy (like "dec" used by app "Simple Cite").
I wonder why they don't use the already existing atlassian-addons user group and assign the app user to it, and the group per default to the space...