Weekly Google Groups governance report

By General Input

Audit your Google Groups every Monday for external members, missing owners, and unlabeled groups, then deliver the full report to your IT team in Slack.

Integrations

  • Google Groups
  • Google Docs
  • Slack Bot

Type

Agentic Task

Categories

  • Operations

Every Monday at 8am, run a governance audit of all our Google Groups and deliver the results as a Google Doc plus a short Slack post.

Step 1, enumerate every group. Use the google-groups List Groups operation to pull every group in our Google Workspace customer.

Step 2, inspect each group. For every group returned, call google-groups Get Group to fetch its label, display name, description, and creation date, and call google-groups List Memberships to fetch its full member roster with roles. Track which members are owners, which are managers, and which are regular members.

Step 3, flag governance issues. Bucket each group into one or more of these categories: groups with external members (any member whose email is not on our primary company domain), groups with zero owners, groups with exactly one owner, groups with no members at all, and groups missing the cloudidentity.googleapis.com/groups.discussion_forum label. A group can appear in multiple buckets.

Step 4, pick the top three risks. Apply judgment to rank the highest-priority issues across all buckets. Weight things like the size of an external-member group, whether an owner-less group has many active members, and whether a group's name suggests sensitive scope (security, finance, exec, all-hands).

Step 5, write the report into a new Google Doc. Use google-docs Create Document to make a new doc titled something like 'Google Groups Governance Audit — <date>'. Then use google-docs Batch Update Document to fill it in. The doc should have: a one-paragraph executive summary at the top, the top three risks called out as a short prioritized list, then one section per issue category with a table of affected groups (columns: group name, email, owner count, member count, creation date, notes). Keep the formatting clean and readable.

Step 6, post the summary to Slack. Use slackbot Send a Message to post to the #it-governance channel. The message should include a link to the Google Doc and the three top risks called out inline so the team sees the highlights without opening the doc. Keep it short, four or five lines.

Make the company domain configurable (default to whatever the authenticated Google account's domain is). The audit is read-only — do not modify any groups or memberships.

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsA searchable RFP answer library your bid team drafts fromLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seats