User Gopher Feature Requests

I use Gohper for Users quite often because of our constant influx of students. I wish my preferred options that I choose when doing my tasks would stay that way. I would like them to either stay as I last used it, or a place that I could set the...

Link or Create a Google Form to put new Users in Fields to Include First Name ,Last Name, Primary Email address and One Time Password ( optional). Once Form Submits, it will go to matching Columns in User Gopher Create User Sheet. Then add tri...

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

I have many emails in my org I wish to not show in the Global Contact Directory for one reason or another. Your only value that can be assigned is "TRUE". I cannot change this TRUE to a blank once it is set at TRUE. It would be great to be able...

Add ability to limit types of generated passwords to comply with complexity requirements. While more complex passwords are not required by Google, we would like the ability to not generate passwords that don't meet our complexity requirements else...

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.

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.

Create a group from every user in /Student/School/Grade 01 etc. This would benefit everyone that does not manage groups via an automated system.

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.