Email workspaceInvitation accepted contract
Purpose/audience: Business administrators receiving the acceptance notice; the named user in the body is the collaborator who accepted.
Implementation: App\Mail\InviteConfirmation. Baseline view: resources/views/emails/users/InvitConfirmation.blade.php. Usage evidence: app/Http/Controllers/Settings/invitationsController.php:756. These are static references, not proof of current production delivery.
Suggested subject: Invitation accepted. HTML title alone does not set the mail header.
Suggested preheader: {{collaborator_name}} accepted your invitation to {{business_name}}.
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. |
| {{collaborator_name}} | $user->first_name + ' ' + $user->last_name | Required escaped full name of the accepting collaborator; not the recipient administrator. |
Content, states and integration decisions
- Preserve the accepting person and business identity. This is an informational confirmation with no source action URL, role list or acceptance timestamp; no button or such fields are added.
- InviteConfirmation does not explicitly set a subject. Invitation accepted is a proposed subject requiring a deliberate header decision during later integration; an HTML title is not an email subject.
- The caller queues mail to each relevant administrator. Keep that audience and avoid greeting administrators with the accepting collaborator’s name. Decorative handshake imagery is omitted.
- States: standard and long accepting-person/business names. No optional identity block should be hidden or replaced with an invented generic account name.
Portable HTML/text and safe handling
ready/invite-accepted.html and ready/invite-accepted.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.