Purpose: As an Organization Administrator, I need to create Configuration User accounts with the power to import, create, and share EAASI resources to my Organization, in order to avoid bottlenecks on staff capacity and generally expand the user base (and related domain- or collection-specific expertise) assisting with resource creation by and for my Organization. However, I also need to mitigate security concerns and the potential for quota/resource abuse by restricting user administration within my Organization (to myself and any other designated Organization Administrators).
Gap Analysis: "Admin" accounts have the functionality specified above in the current EAASI UI, and are accurately limited to adding or designating user accounts as "Configuration User" accounts within the Organization of the logged-in Admin account. The “Manage Node” and “Node User Administration” labels however are misleading and should be switched to reflect “Organization”-level management when an Organization Admin is logged in.
Configuration Users accurately see resource creation and management functionality but not deployment or Organization-level user management screens when they log in to the EAASI UI. Review should be done to confirm they also lack proper permissions to trigger user management tasks via demo UI/API/etc.
Purpose: As an Organization Administrator, I need to create Configuration User accounts with the power to import, create, and share EAASI resources to my Organization, in order to avoid bottlenecks on staff capacity and generally expand the user base (and related domain- or collection-specific expertise) assisting with resource creation by and for my Organization. However, I also need to mitigate security concerns and the potential for quota/resource abuse by restricting user administration within my Organization (to myself and any other designated Organization Administrators).
Gap Analysis: "Admin" accounts have the functionality specified above in the current EAASI UI, and are accurately limited to adding or designating user accounts as "Configuration User" accounts within the Organization of the logged-in Admin account. The “Manage Node” and “Node User Administration” labels however are misleading and should be switched to reflect “Organization”-level management when an Organization Admin is logged in.
Configuration Users accurately see resource creation and management functionality but not deployment or Organization-level user management screens when they log in to the EAASI UI. Review should be done to confirm they also lack proper permissions to trigger user management tasks via demo UI/API/etc.