Fix MailSec beta onboarding and enforcement guidance - #442
Merged
Merged
Conversation
lcbill
approved these changes
Sep 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix the onboarding gaps found during the first Google Workspace beta setup: explicit pilot scope in all three examples, Python CLI installation from master, analyst force overrides in alert-only mode, Gmail banner limits, reciprocal credential-envelope warnings, DRS remediation and verification, and backfill recovery/retention cleanup guidance.
Replace credential-bearing command arguments across Email and Cloud Security with jq/stdin envelopes and remove temporary files after successful storage. Correct the enforcement claims in policy, messages, and CLI setup. Explain that retention deletion is asynchronous, requires an enabled sweeper, and first reports a changed horizon before deleting.
The zero-update asymmetry remains unreproduced; troubleshooting asks for submitted data and readbacks rather than treating an etag as proof of a particular server branch. No Python release is required for this beta workflow.
Validation: MkDocs build passes; credential stdin round-trip preserves escaped private-key bytes. Existing unrelated release-note anchor notice remains.