I got problems configuring other users but default for accessing Genesys Administrator.
The user i want to access Genesys Administrator is in administrators Access Group, which is assigned for the role wcm_admin. so he s permitted to access the wcm application object with full control. nevertheless genesys administrator says:
Access to Genesys Administrator is denied. Please Contact System Administrator.
As this is supposed to be me, im kinda stuck. What could be missing?
I had the same issue when I first installed it. The “problem” revolves around the “role-based access” of Genesys Administrator.
First, make sure your Config Server is up to date (8.0.2 at least)
Then
-Create New User
-Make new user a member of “Administrators” group
-Create New Role Called WebAdmin
-on Role Priviledges selected check box for “Genesys Administrator”
-then chose “Allowed” for each of the role options required for new user
-added your new user as a member of “WebAdmin” role (for you testadmin)
I notice one odd behaviour pertaining to GA where the Role Privileges will disappear for the role i assign to users to access GA. I’ve set Allow All for all the modules and sub modules but after awhile (can’t manage to pinpoint when/how) only the Deployment module will have the Allowed value while the rest will be unassigned.
I have also observed this exact behaviour… I will let you know exact versions tomorrow to see if our problems correlate. Unfortunatly I don’t know of a fix yet.
I guess this thread is kind of old, but for the sake of future references here are some additional things you should check:
That the new user has some kind of access group with R/X access (read/execute) to the most top Configuration Folder.
The Roles granted to new user are coherent. In the “Genesys Administrator - Modules” you must allow each module that you want allowed as a child (eg. you get this error if you don’t allow “Genesys Administrator - Modules”=Monitoring but then allow “Genesys Administrator - Monitoring”=“Outbound Monitoring”. Be careful as the tool does not check the consistency of you Role definitions (No warnings!).
If you are using a multi-tenant environment, be very carefull as access groups roles membership is pretty easy to mess up. Use only the access groups and Role from the Environment tenant, Always! This one is really counterintuitive if you’re used to CME.