We just upgraded to ALM12 and want to restrict/allow ”ALM Web Client” access by Project and/or Group, can we do that?

  • Questions
  • We just upgraded to ALM12 and want to restrict/allow ''ALM Web Client'' access by Project and/or Group, can we do that?
Question ID: 106202
0
0

We are trying to selectively roll-out the new Web Client, but don’t want to expose it to all users and if possible, even enable it project-by-project.
Can that be controlled somehow?

Marked as spam
Posted by (Questions: 185, Answers: 13)
Asked on July 22, 2015 8:05 pm
2 views
Answers (1)
0
Private answer

YES!

There is a NEW set of PERMISSIONS for each QC Group.
In the Administration tab of the Group permissions (on a User-created group, not caned ones), you can select what level of access (full, view, none) that group has to the Web GUI (cross-platform client) of QC.

Out of the box, the built-in groups (TDAdmin, Developer, Project Manager, QATester, and Viewer) have FULL access rights here.

You *could*, with the use of tweaks to your user-defined groups in your various projects, LIMIT access by project and by-group as you roll out the new Web GUI client - REMEMBER: it has its OWN/separate Workflow than the ''traditional'' IE client).

See attachment on note

Marked as spam
Posted by (Questions: 3, Answers: 466)
Answered on July 22, 2015 8:11 pm