Obsolete
Status Update
No update yet.
Comments
bl...@google.com
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...
jp...@google.com
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config assign for component 191635.
Description
Description
Asking for the "posting" setting to a subscription in groups for the Reports API to be similar to the the
Impact
Currently if a person with admin access to a group changes the ability of a user to post (allowed/moderated/not allowed) it is not logged.
This would be useful in a similar way to the "change_email_subscription_type" event.
This means there is no record of the action (ie no userid or date/time logged) to track the change in an audit or report.
This also means that the events do not appear in the admin.google.com reporting and that also means altering of an unauthorised change is not possible.