= bug description =

As discussed on the list, I'd like to have FAS groups to control shell access to the automation machines, which is needed in many cases for folks to develop and triage tests.

== User groups ==
* qa-taskotron-user
* qa-beaker-user

These groups would need to provide shell access to bastion-comm01.fedoraproject.org so that users can ssh into test clients.

The users do not need to be able to get into bastion01 or lockbox01 or any of the sysadmin resources. Sysadmin activities for the automation systems would continue to be provided by the sysadmin-qa group.

Alternatively, shell access could be provided by a qa-automation parent group, if that is a better/easier way of granting shell priveleges.

== Admin groups ==
* qa-taskotron-admin

Currently, beaker has no way to query FAS for group membership, so it can be managed with just a -user group and any farther permissions will be managed using beaker's internal group management.

However, taskotron will need an admin group to control access to admin-type functionality.