Payroll access revoked contract

Purpose/audience: The affected collaborator whose payroll access was revoked (invite user_email).

Implementation: App\Mail\UngrantPayroll. Baseline view: resources/views/emails/users/UngrantPayroll.blade.php. Usage evidence: app/Http/Controllers/Settings/invitationsController.php:1958. These are static references, not proof of current production delivery.

Suggested subject: Payroll access revoked. HTML title alone does not set the mail header.

Suggested preheader: {{business_name}} has revoked your payroll access on Built.

Portable placeholder contract

Token	Existing source / derivation	Requirement
{{logo_url}}	Existing Built app_name PNG	Optional deployment override; the concrete project HTTPS PNG is the default. Approved HTTPS or matching CID only.
{{preheader}}	Suggested text above, assembled only from already available values	Required escaped text; not a new backend record or processing guarantee.
{{business_name}}	$business->name	Required escaped business identity; do not substitute the recipient name.

Content, states and integration decisions

Explicitly retain that the recipient can no longer access this business’s payroll. Do not imply that their whole Built account, all businesses or unrelated permissions are revoked.
No source action URL, recipient name, reason or timestamp is supplied. The draft adds none and has no action button.
UngrantPayroll does not explicitly set a subject. Payroll access revoked is a proposed subject requiring an explicit integration decision. The caller queues the Mailable; preserve its current sender defaults.
States: standard and long business name. The source business identity remains present without a duplicate sign-off.

Portable HTML/text and safe handling

ready/payroll-revoked.html and ready/payroll-revoked.txt provide the portable extracts. Every populated state has matching .html and .txt files under previews/. All sample links are local design explanations; no real invitation, report or account action is executed. Placeholder {{names}} are not automatically Laravel Blade syntax. Convert each mapping explicitly using existing data and server-side URL generation; retain all required values and do not insert untrusted raw HTML.

Escape text and attribute values. Validate any application/CFO AI URL separately against approved HTTPS hosts before escaping it; preserve complete generated links and encrypted/signed parameters. Use the provided concrete public PNG or an approved HTTPS/CID override. There are no hidden optional content sections to populate here; required identities/counts should not be silently omitted. Unsupported data has not been invented.

All drafts use the approved compact transactional shell with 16px body text, a minimal Built footer and native light/dark CSS. Email-client rendering and blocked-image behavior remain separate tests. See integration-notes.html for shared provider/image limitations, and easy-wins-batch.md for the whole batch. No production template, sender, transport or application behavior is changed.