- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

In our 4.3 environment we're unable to give specific users permissions to run the getting started wizard. We want to be able to give this permission to a specific user but prevent them from seeing all of the applications in the controller. They should only see the application that they normally see in the apps list. It looks like this permission is built into the account owner role but isnt able to be split up. In our 4.2 environment we have no problems giving specific users access to the getting started wizard but no access to non authorized apps.
Is this possible to do in 4.3?
When we create a role we will give them all edit permissions to a specific app but giving solely this does not enable them to deploy their own java agents. This setup currently works in our 4.2 environment.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We understand that these should be decoupled, have an ongoing enhancement request to have seperate permissions for "Administer user" and "Use Getting Started Wizard".
Here is the enhancement request id UIPLAT-99. This feture will be avaliable in future versions.
Regards,
Pratik
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can do so by providing the below two permissons to the newly created role.
- Administer user, group, roles, authentication, etc. View Appdynamics Agent. Use Getting Started Wizard.
- View and configure licenses.
To manage Application for that role you may configure Applications options. Do refer attached screens.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Thanks for your response. I wish it was as easy at that but the users should never be able to see the other applications or the admin console, as they can easily change roles and user permissons without approval. Your solution meets the requirements of just access to their application but with that setup the users could just go in and make all the local accounts they want and whatever roles they want.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We understand that these should be decoupled, have an ongoing enhancement request to have seperate permissions for "Administer user" and "Use Getting Started Wizard".
Here is the enhancement request id UIPLAT-99. This feture will be avaliable in future versions.
Regards,
Pratik
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hi Pratik,
When can we expect UIPLAT-99 to be in production? Is there a release date or a release version for this to be implemented?
Thanks,
Aaron
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Aaron,
Currently, the feature request is with the project management team and they will be further prioritizing it. We do not see any updated ETA regarding the request
-Thanks
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is this enchantment request across the board, or per site? We really don't feel comfortable having to give users access to overide their account permissions or even worse the ability to change our admins passwords and permissions.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Thanks for the update! Just find it weird it works perfectly in my 4.2 environment that way. Even though apparently the getting started wizard was associated with the same items but maybe it just wasnt implemented properly on our setup.
