Corporate admin guide
Everything you need to manage your organisation’s TheWILL.ai corporate benefit programme. Invite employees, monitor engagement, and keep your programme running smoothly.
Last reviewed
Inviting employees
There are multiple ways to invite employees to your corporate benefit programme. Choose the method that works best for your organisation.
When every licence is in use, the corporate dashboard and Employees list show that all your licences are in use (for example “All 10 licences are in use”), with a Request more seats button for your account owner and billing contacts, and we email your administrators, at most once a day, whenever someone is turned away for lack of a licence.
Email invitations
- Open the invite pageUnder Corporate Dashboard in the sidebar, choose Invite. It sits alongside Employees, and the Employees list also has an Invite employees button.
- Enter employee email addressesPaste one address or many, separated by commas, semicolons or new lines. To record an employee ID from your HR system, put it after the address on the same line, separated by a comma (alice@company.com, EMP-001). The Invite page tells you the maximum a single batch accepts. Employees receive an invitation email with a link to activate their benefit.
- Track invitation statusThe Employees list shows each person as Invited, Expired, Active or Deactivated, and can be filtered by Invited, Active or Deactivated.
Domain-based auto-enrolment
Configure your organisation’s email domains in Settings and verify each one. Once a domain is verified, any new user who registers with a matching email domain will automatically be prompted to activate the corporate benefit.
Once you have verified at least one domain, invitations to addresses outside it are rejected, so keep the list complete.
Expiry and resending
Invitations expire a set number of days after they are sent, and each link is tied to the address you invited, so it cannot be forwarded to a colleague. Resending an invitation restarts that window.
An invitation that lapses unanswered stays on the Employees list as Expired, with a Resend button beside it. Lapsed invitations also trigger an email to the administrator who sent them, at most one a day for your organisation, pointing back to the list so you can send them again.
Invitations to new administrators work the same way. They are listed on the Team page under pending invitations, each with its expiry date, and an expired one shows Expired with a Resend button; resending issues a fresh link and expiry. If an administrator invitation lapses unanswered, the person who sent it is emailed once, pointing to the Team page. An expired invitation holds no admin seat, so resending it is refused if your organisation has since reached its administrator limit.
CSV import
- Prepare the fileSave a CSV with an email column and, optionally, department and employee_id columns. A file can hold up to 500 rows.
- Upload it on the invite pageUse Import from CSV on the Invite page. The file is checked first: you see how many rows are ready and every problem listed by row number, such as an invalid or repeated address, before anyone is invited.
- Confirm the importChoose Invite to send invitations to the valid rows. Rows refused at this point, for example because no licences are left, are listed by row number too, so you can fix them and import them again.
Exporting your employee list
Reading usage reports
The corporate dashboard provides aggregate usage statistics to help you understand programme engagement. Overview and Adoption usage figures are aggregated, so you never see which employee did what. Trends counts activations and deactivations exactly, because they come from your employee list, which already shows each employee’s status.
Available reports
- Overview: activated employees on your roster and the seats in use against your licence (an invitation holds a seat until it is accepted or expires), plus counts of wills started, wills completed, documents uploaded, video messages recorded and legal reviews booked
- Trends: new activations, deactivations and the running active total by week, month or quarter (monthly by default), over the most recent months
- Adoption: which features employees are using, with an adoption percentage for each
- Employees: each employee’s work email, department, employee ID and status (Invited, Expired, Active, Deactivated), with the same columns available as a CSV export
Privacy protection
Who can see which report
Screenshot, for illustration only




Managing email domains
Email domains control which users can be automatically recognised as employees, and which addresses you are allowed to invite. Manage your domains in Settings under Corporate Dashboard. Only the account Owner can change them.
Adding a domain
Add your organisation’s email domains (e.g. “company.co.uk”) and choose Verify domain to prove your organisation controls each one; automatic employee recognition stays off for a domain until it is verified. Once it is, when a user registers or signs in with a matching domain, they’ll be offered the corporate benefit.
Removing a domain
Removing a domain does not affect existing employees who have already activated their benefit. It prevents new users with that domain from being auto-recognised, and stops you inviting new addresses at that domain. To switch it back on, verify the domain again.
Offboarding employees
When an employee leaves your organisation, you can deactivate their corporate benefit from the Employees list.
What happens when you deactivate
- The employee loses access to corporate-tier features
- Their account, will, and documents are NOT affected
- They can continue using TheWILL.ai with a personal subscription or free tier
- If they had a previous personal subscription, it resumes automatically and they are emailed to say so
- You cannot access or delete any of their will, documents or account data
- Their row stays on your Employees list marked Deactivated, so the seat is released and the history is preserved
Reactivating someone who rejoins
A deactivated employee can be reactivated from the same list, provided your contract has not expired and you have a seat free. Reactivation starts a fresh corporate subscription and sets any personal subscription aside again: a free plan is paused, and a card-paid one is ended and the unused part refunded.
Choosing not to renew
An Owner or Billing admin can choose Don’t renew on the Billing page, and undo it there, until the cutoff the page shows before the contract end date. While a renewal request is open, the page hides Don’t renew. After that the next term is due and the page says so. A plan billed by card renews by itself on its renewal date; a plan paid by invoice is renewed when its renewal invoice is paid.
When the contract ends
- If your contract is not renewing, each covered employee is emailed before their cover ends
- Everything keeps working for a grace period after the end date
- After the grace period every remaining active employee is deactivated in the same way. Nobody loses data, and anyone with a paused personal subscription has it resumed
- Single sign-on, SCIM, reporting API keys, webhooks and your branding switch off at the same time
- Renew soon after the end date and the employees the expiry deactivated come back automatically, up to your seat limit, with your integrations switched back on
- If the contract is not renewed in that window, your organisation’s settings are deleted: branding, single sign-on and SCIM setup, API keys, webhooks, campaigns and your onboarding checklist, and your verified domains are released. Employees’ own accounts, wills and documents are never touched
Important
Automatic provisioning with SCIM
If your organisation manages people in an identity provider such as Okta or Microsoft Entra ID, you can connect it with SCIM 2.0 so that seats follow your directory instead of being invited by hand.
Connecting your identity provider
- Open settingsUnder Corporate Dashboard in the sidebar, choose Settings and find the SCIM provisioning card.
- Create a tokenGive the token a name you will recognise, such as the name of your identity provider, and choose Create token. Copy the token straight away: it is shown once and cannot be retrieved later.
- Configure your identity providerIn your identity provider, add a SCIM application using the SCIM base URL shown on the card and the token as the bearer token, then assign the people who should hold a seat.
What provisioning does
- Assigning someone in your identity provider invites them to activate their corporate benefit
- Unassigning or suspending someone deactivates their seat, exactly as deactivating them from the Employees list does
- Their account, will and documents are never deleted by provisioning, because they belong to the employee
- Groups pushed from your identity provider are kept in step, and where seat groups are set up for single sign on, membership of those groups decides who holds a seat
Revoking a token
Setting up the connection yourself? The SCIM provisioning reference lists the endpoints, the attributes we read, the supported filters and PATCH operations, and the errors your identity provider may see.
HR system sync
If your HR system, or the middleware in front of it, can send your current staff list, it can keep seats in step for you: new starters are offered a seat and leavers’ seats are released.
Connecting your HR system
- Open settingsUnder Corporate Dashboard in the sidebar, choose Settings and find the HR system sync card.
- ConnectChoose Connect HR system. Copy the signing secret straight away: it is shown once and cannot be retrieved later. Choose Rotate secret on the card at any time to replace it; the old secret stops working straight away, so update your HR system first or straight after.
- Configure your HR systemHave your HR system send its full staff list to the roster URL on the card, signed with the secret and carrying the two signature headers the card names.
What sync does
- Someone new on the staff list is invited to activate their corporate benefit
- Someone no longer on the list has their seat released, exactly as deactivating them from the Employees list does. Only seats HR sync has seen on a list are released: seats you invited yourself or imported stay put until their email first appears on a list
- An invitation that expired before it was accepted is sent again while the person is still on the list
- Anyone the sync could not apply is listed on the card with the reason
- Seats your identity provider manages through SCIM are never changed by HR sync; the card lists any it left alone
- Their account, will and documents are never deleted by sync, because they belong to the employee
Sync now and disconnecting
Reporting API
If you want your own HR or reporting tools to read your programme figures without anyone logging in, create a reporting API key. A key reads only what you choose when you create it, and no key can ever read an employee’s will, documents or estate plan.
Creating a key
- Open settingsUnder Corporate Dashboard in the sidebar, choose Settings and find the API access card. Only programme owners can create keys.
- Choose what the key can readTick Reporting, Roster, or both. Then pick how long the key lasts from Expires after. Every key expires, so you will need to create a replacement before then.
- Copy the keyName the key and choose Create key. Copy it straight away into your system: it is shown once and cannot be retrieved later.
What a key can read
- Programme reporting: overview, trends and feature adoption, with small groups suppressed exactly as on your dashboard, plus your invoices
- Employee roster: the work email, department and employee ID you provided, each seat’s status, and its invitation, activation and deactivation dates
- Send the key as a bearer token (Authorization: Bearer followed by the key) to the endpoints under /api/v1/corporate/ext/: overview/, trends/, feature-adoption/, roster/ and invoices/
- The roster is paged and can be read incrementally with updated_since, so a nightly sync fetches only the seats that changed
Keeping keys safe
Embed on your intranet
With white label switched on, programme owners and admins can put a button on your intranet or staff portal that opens your branded join page. Find it under Settings, in the Embed on your intranet card.
- Copy the widget code from the card and paste it into a page on your intranet
- Add the address of each website that will show the button; it appears only on the websites you list
- The button carries only your public embed id, never a key, and reads nothing about the person viewing the page
- If white label is switched off or your contract ends, the button stops showing
Custom domain
The Custom domain card in Settings lets owners and admins of a white label programme add a web address of your own, such as benefits.example.co.uk, for your join page and your employees’ dashboard.
- Enter the address, publish the DNS record or file the card shows to prove you own it, then choose Check now
- The badge shows where it stands: Waiting for verification, Verification failed, Switching on soon or Live
- Switching on soon means custom domains are not switched on for your programme yet; your address starts serving once they are
- Removing the domain asks you to confirm first; you would need to verify it again to add it back
Privacy model
The Employer Programme is designed with employee privacy as a core principle. As a programme administrator, you should be aware of the following:
- You have NO access to employee wills, documents, video messages or estate details
- You do see the administrative record you supplied: each employee’s work email, the email on their account, their department and employee ID, and their status
- Usage figures on Overview and Adoption are aggregate statistics, never who did what; Trends counts activations exactly from the roster you already see
- Overview usage figures stay hidden until enough employees have activated, and small adoption counts are suppressed rather than shown
- Employees can contact support independently, and you won’t be notified
- Data remains with the employee if they leave the organisation
Administrative actions such as inviting, deactivating and reactivating an employee are written to an audit log that Owner and Admin roles can read, and that record names the employee.
If you need assistance with your programme, contact your dedicated account manager. Their details are available on the Corporate Settings page.
Related topics
Can’t find what you’re looking for?
Our support team is here to help. Contact us and we’ll get back to you as soon as possible.
Contact us
