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: In our university, the inconsistent formatting of email IDs has posed numerous challenges. There is a pressing need for administrators to standardize email creation processes to ensure uniformity and efficiency. Currently, there is no streamlined method for defining whether an email serves an individual or an office within the organization, leading to confusion and inefficiencies in communication. Additionally, the lack of predefined access permissions for office emails and the absence of auto-generation options for personal email IDs result in irregularities and inaccuracies.
Desired Behaviour: The desired behaviour involves empowering administrators within Google Workspace to standardize email creation and management processes effectively. Administrators should have the ability to define whether an email serves an individual or an office, with the option to specify access permissions (tagging users to handle the office account) within the space of the office account. Personal email IDs accepted by the organization should adhere to predefined formatting rules, such as First Name, Last Name@domain, to prevent irregularities and ensure consistency. Office emails should be associated with specific buildings or resources, facilitating efficient management and organization of workspace data.
Possible Solution: To address these challenges, Google Workspace could implement features that enable administrators to define email types (individual or office) and specify access permissions within the organizational structure. Additionally, incorporating auto-generation options for personal email IDs based on predefined formatting rules would streamline the email creation process and minimize errors. Office emails could be linked to specific buildings or resources, providing a clear framework for managing workspace data and facilitating efficient communication and collaboration.
Impact
The implementation of these features would have a transformative impact on email creation and management within Google Workspace. Administrators would experience greater control and efficiency in standardizing email formats and managing access permissions. Users would benefit from streamlined communication processes and enhanced clarity in responding to office matters. Overall, these enhancements would optimize productivity and facilitate seamless collaboration within the organization.