GRP-14: Use a group to control access within an application

Executive Summary: 
A community member needs to use a community group to control access within an application. Notable reasons include: a campus or L3 service offers services to specific community members, a science gateway offers group-based access control to gateway functions or resources, a project member limits access to a project tool (or administrative privilege within a project tool) to members of a project’s WBS group.
User Importance Summary: 
Community members need to be able to define arbitrary groups of people to which they can refer for authorization and communication purposes. Researchers need these groups to be visible/usable within applications, science gateways, and campus IT systems (in a campus bridging scenario).
Target Communities and Sizes: 
Science gateway and application developers - 100 < N < 1,000 Campus IT administrators involved in campus bridging - 100 < N < 1,000 Independent resource providers - 100 < N < 1,000