User Gopher Feature Requests

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...

Schools that define their own custom schemas need easier methods to update these schema values. Examples of custom, school-defined attributes could be information like Student ID, Graduation Cohort, Homeroom, Faculty Advisor, etc. and these field...

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...

I am resetting our elementary passwords and I am doing it by school so that the tickets match the school. I would be nice to have in the email a description so that I know what group that particular group of password tickets belong to - I use grad...

On the email ticket, I think it would be great is Create New Password is set to true for a user, then on the ticket let them know that they will have to create a new password.

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.

Some folks may be using this field to hold additional information about students, so why not include it?

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.

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.