As a Deployment Administrator or Organization Administrator, I need to restrict access to a resource that has been made available to multiple users

[mswendyh]

Purpose: As a Deployment Administrator or Organization Administrator, I need to make an Environment that is currently available to other users private again (restrict access to that Environment) so that I can comply with policy requirements.

Restricting access to an Environment that is currently available to other users:

• The Deployment Administrator or Organization Administrator locates the Environment that is the target for access restriction and selects a “Nominate for Access Restriction” option.
• The system identifies derivative environments that have been created based on that Environment across the Deployment and notifies both the Deployment Administrator (or Organization Administrator) who nominated the access restriction and the Organization Administrators of other Organizations in the Deployment that have saved derivative Environments based on the Environment nominated for access restriction.
• After this notification step, the actual access restriction must then be triggered by the Deployment Administrator or Organization Administrator who nominated the change. This restriction should result in the Environment becoming Private to that Deployment Administrator or Organization Administrator who nominated the change.
• (Should there be a need for the Environment that is now private to be made available to other users within the nominator’s Organization, that Organization Administrator can follow the appropriate steps to make that Environment available as needed, as described in other User Stories.)

Gap Analysis: Currently, it is not possible from the EAASI UI to make resources that are currently available to other users private again or otherwise restrict access once they have been Published.