User Gopher Feature Requests

Similar to Group Gator, Administrators to delegate the ability to certain tasks, like change password, to a specific Group/OU, without the need to give them the appropriate Admin Privilege in the Admin Console.

Allow an Administrator to delegate the ability to use certain functions without requiring full access. This could be done using multiple Admin Roles to restrict which Write actions could be performed. It would also require sending only the permi...

Build a new tab in which users are listed vertically and a column exists for each domain group with a "Yes" for group membership.

This would be something that requires an API change at Google, as this is not presently possible. Useful because it would allow for workflows that might remind students to transfer their data who haven't yet, and ensure minimal harm when deleting...

Using Gopher easily manage alias accounts in bulk fashion, used for district clean up and yearly alias maintenance.

This would be helpful to create "id" cards, using a mail merge. I cannot always email the new password for a new user, if the student has never had an email before.

Examples: "Delete all users in a specified OU 1 year from now" "Delete all users in a specified OU after 1 year of inactivity" etc.

It would be comforting for the user to be able to see exactly what will be sent to a user in the body of the pw reset email before sending it.

Create new user and add an alias for name changes or multiple domains

Create a rule-builder that enforces automated actions on users on a daily time-based trigger, and logs / notifies the admin of actions taken. Examples: Any user whose OU includes "Student" should be auto-removed from the contact directory Any us...