Invite a Whole Team in One Go
Onboarding ten people one at a time gets old fast. The bulk invite wizard sends setup links to up to 500 recipients at once — paste a list, optionally allocate storage per person, hit send, and let each new user pick their own password from the invite email.
When to reach for this
- You're migrating a 30-person team onto TrekMail and want to skip the manual click-through.
- An agency is onboarding a client whose whole company needs mailboxes by Monday.
- A school year is starting and you have a roster CSV.
- You want each user to choose their own password — bulk creation (where the admin sets passwords) doesn't fit your workflow.
Where to find it
Go to Mailboxes, open the Add mailboxes menu, and choose Bulk invites. The wizard accepts either a pasted list of recipients or a CSV upload.
Two ways to feed it data
-
Pasted list — one recipient email per line. The local part is derived from the recipient email (everything before
@); the wizard previews each generated mailbox before you send. - CSV upload — same idea with one extra column. Each row carries a recipient email and, optionally, a dedicated storage allocation in megabytes (handy if you want a CEO mailbox at 20 GB and everyone else on the shared pool). The wizard shows what each row will become before anything is sent.
Either way, the preview step is your safety net — invalid emails, duplicate addresses, and over-quota allocations are flagged before any invite goes out.
What the recipient sees
Each person gets an email with a single setup link. They click it, set their own password, and land in webmail ready to go. Until they redeem the link nothing is provisioned — no storage held, no aliases attached. The default link expiry is 30 days; you can set a shorter window per-batch in the wizard.
Limits to keep in mind
- Up to 500 invites per batch through the wizard.
- Total mailboxes (existing + pending invites + this batch) must fit your plan's per-domain mailbox cap — the preview shows what's left before you submit.
- If you assign dedicated storage per row, the sum across the batch can't exceed your account's available storage pool.
- Each invite link is single-use; resending an unredeemed invite issues a fresh link from the wizard's pending list.
vs. Bulk mailbox creation
Bulk invites and bulk creation look similar but differ in who sets the password. With bulk creation you ship a CSV that includes passwords (or generated ones) — the mailboxes exist immediately, ready for IMAP. With bulk invites the recipient picks their own password, which is usually what an end-user prefers and what compliance teams want. Pick the one that matches how your users will receive credentials.
Automating it
For an HR system or onboarding pipeline that should fire invites without a human in the loop, the same surface is available through the REST API and the MCP tools. POST /api/v1/mailboxes/invites:bulk and the create_invites_bulk MCP tool both accept up to 100 items per call — chunk a longer list yourself. Each item takes local_part, recipient_email, and optional storage_allocation_mb. See the API overview for the request shape and authentication.