Settings and activity
14 results found
-
8 votes
richard.martin@jll.com
supported this idea
·
-
49 votesrichard.martin@jll.com
supported this idea
·
-
18 votesrichard.martin@jll.com
supported this idea
·
-
11 votesrichard.martin@jll.com
supported this idea
·
-
106 votesrichard.martin@jll.com
supported this idea
·
-
30 votesrichard.martin@jll.com
supported this idea
·
-
20 votesrichard.martin@jll.com
supported this idea
·
-
20 votesrichard.martin@jll.com
supported this idea
·
-
71 votesrichard.martin@jll.com
supported this idea
·
-
28 votesrichard.martin@jll.com
supported this idea
·
-
141 votes
An error occurred while saving the comment richard.martin@jll.com
supported this idea
·
-
22 votesrichard.martin@jll.com
shared this idea
·
-
92 votesrichard.martin@jll.com
supported this idea
·
-
120 votesrichard.martin@jll.com
supported this idea
·
With SSO and LDAP authentication it is difficult for System Admins to troubleshoot errors that their end-user experience. The only option they have is to work with the user to find a time that works for both parties to have a working session, A lot of times these end up being fact-finding sessions which are followed up with another session for implementing resolution and testing. To work with another System Admin to set their Role to match the user having issues, which is not ideal. The last option is to hope that the same issue exists in the Development or Staging environment if they are not protected by SSO/LDAP. It would be nice for a future release to have the ability, as a System Admin, to proxy as another user/role in these secure environments.