Conversation
…fore a deletion An organization could be told what Email Security deletes and when, but not that its own data was already scheduled to go — and nothing anywhere said what a free trial is, how long it runs, or how many mailboxes it covers. policy.md gains a plans section (14 days, 25 mailboxes, what happens at expiry, and that unsubscribing and resubscribing does not restart the clock) and the retention section now names all three ways a deletion is scheduled, what cancels each one, and the two notices that arrive before it fires. getting-started.md says it where a new organization will read it: at the subscribe step, and again at coverage, with the entitlement block that turns "how much of my estate is not covered" into a number.
Contributor
Author
|
/lc-review |
lcbill
approved these changes
Sep 7, 2026
maximelb
added a commit
that referenced
this pull request
Sep 7, 2026
- policy.md: took master's 'It also happens without a request' table and its 'You are told before it happens' section wholesale; they are strictly better than the version this branch had and cover cancellation non-interchangeability. - policy.md: fixed two links to api-reference.md#get-coverage, an anchor that does not exist. They arrived on master with #382 and neither mkdocs --strict nor the repo's check-links job validates fragments. - troubleshooting.md: dropped the hedge about trial limits now that the terms are published, and cross-linked the plans section instead. Added the three mailbox-cap fields the coverage layer adds on top of the entitlement RPC (mailboxes_active, mailboxes_over_cap, mailbox_cap_reached), and called out that a lapsed trial keeps the API while an unsubscribe does not.
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.
Board: [Pre-GA] W7 org lifecycle. Public repo — open for review, not to be merged without Maxime's go-ahead.
Why
Two gaps a customer would hit in their first week:
policy.mdalready explained what a tenant purge deletes and that an unsubscribe schedules one 30 days out — but not that the customer is told before it happens, and not that a lapsed trial schedules one too. The whole point of a 30-day grace is that it is recoverable, and a grace nobody is told about is not one.What changed
policy.mdFINAL NOTICEseven days before it fires, and theentitlementfields onGET /coverageto read the countdown from at any time.getting-started.mdentitlementblock, withmailboxes_over_capcalled out as the number that matters: those mailboxes were found and are not being watched.Notes
No feature is documented ahead of itself: the backend is in review at the same time, and this PR should land with it. Nothing here names a price — pricing is deferred, and the trial is described in terms of the free tier the platform already has.