Assigned
Status Update
Comments
bl...@google.com <bl...@google.com> #2
Metadata
- Summary: The Directory API's users.list method is inconsistently returning a nextPageToken when using the query parameter, and the starts with operator is not working for the orgDepartment field.
- Tags:
,directory-api ,users-list ,next-page-token ,query-parameter ,org-department starts-with-operator
Additional resources:
https://issuetracker.google.com/savedsearches/566232?hl=it https://developers.google.com/drive/api/reference/rest/v3/files/list https://developers.google.com/admin-sdk/directory/v1/.../manage-users https://developers.google.com/admin-sdk/directory/reference/rest/v1/.../list https://stackoverflow.com/.../want-admindirectory-users-list-more-then-500... https://stackoverflow.com/.../drive-list-files-doesnt-have-nextpagetoken-wh... https://stackoverflow.com/.../how-to-resolve-the-missing-information-probl...
Description
Before opening a new issue, please search for other related issues , click the ★ to subscribe to updates, and click
+1
to vote.Description
Problem Statement: The current functionality of the "EMAIL" button within Google Workspace user accounts presents limitations for effective communication, particularly for administrators. While functional on Windows 11, users on alternative platforms, such as Ubuntu 23, face challenges with setting default email applications, rendering the button ineffective. This feature is vital for conveying important information to users, not for socializing. Thus, there's a pressing need to enhance its capabilities.
Desired Behavior: I propose implementing an automated email formatting system triggered by the "EMAIL" button. This enhancement would allow administrators to effortlessly send invitations to new users or notify existing users of any changes made to their accounts. Additionally, introducing a pre-setting option within the Google Workspace Admin Console would empower administrators to define the default behavior of the "EMAIL" button, streamlining communication processes for all users.
Possible Solution:
Introduce a pre-setting feature in the Admin Console to define the default behavior of the "EMAIL" function (auto-sending or manual). Enhance the "EMAIL" button to serve as a communication tool for informing users about changes to their accounts. Ensure the functionality only operates if a validated alternative external email is provided by the user. Automatically populate the recipient's email address with their alternative email associated with their Google Workspace account, eliminating manual input. Standardize the email content to include a comprehensive list of user account information for new users and highlight changes for existing users. Possible Alternative: If implementing default email application settings proves challenging, an alternative solution could involve integrating the "EMAIL" button functionality directly within the Google Workspace Admin Console. This would replicate the user-friendly experience of Google Docs' "Email Collaborators" feature, enabling administrators to send emails without relying on external applications.
Impact
Enhancing the email functionality within the Google Workspace Admin Console is essential for improving communication efficiency and transparency within organizations. Users have the right to be informed of changes to their accounts, fostering trust and security in e-communication. By implementing the proposed features, we can ensure a seamless user experience for administrators and effective communication with users.