← سند dashboard All docsPublished copy (redacted) of sanad/onboarding/ALIAS-RUNBOOK.md · source updated 2 Nov 2026 19:30 Riyadh · synced 4 Nov 2026 05:16
Client email alias runbook (Bandar, 2 Nov 2026 3:34 PM)
- DEFAULT for every client: alias [email removed] on the existing [email removed] Microsoft 365 mailbox. No DNS change, no spend.
- Add it as an extra address on the [email removed] mailbox (Microsoft 365 admin, needs an admin sign-in). STOP and tell Lead if it needs DNS or spend.
- Link it to the client ID in profile.md and in the Notion row; put it on CVs once the client confirms.
- Test delivery: send a test email to the alias and confirm it lands in [email removed].
- Clash: if the name is taken, use firstname.lastname2.
- Offboarding (8.2): remove the alias from the mailbox and log it.
Standing rule (Bandar, 2 Nov 2026 3:37 PM, relayed by سند Lead)
- For every new client, سند Lead adds the [email removed] alias to the [email removed] M365 mailbox on Bandar's behalf, without asking him first.
- Onboarding asks Lead for the alias, then runs the test delivery (send to the alias, confirm it lands in the [email removed] inbox) and puts the alias on the CVs.
Employer job-site accounts (standing rule)
Standing rule (Bandar, 2 Nov 2026 ~7:07 PM, relayed by سند Lead): سند · Applications creates employer job-site accounts (e.g. Workday) with the client's سند alias when a job needs one. When Applications asks, Onboarding reads the verification email in [email removed] (read-only, nothing replied/moved) and passes only the link or code directly to Applications by private agent message, never in the group room or any shared chat, and never stores it in files or logs. Account passwords are never shared with clients.
See also: CLIENT-DATA-RUNBOOK.md (where everything a client sends gets saved).