What is a User in TNZ?
In TNZ, a User is any email address that's authorised to send messages through your account. The User record can have a dashboard login and API credentials.
- Authorised sender (sending via Email-to-SMS, Email-to-Fax, Email-to-Voice, and similar tools)
- Dashboard login at my.tnz.co.nz
- API credentials
📩 A User is not a recipientYou don't need to add the people you're sending to as Users, and you can send to any mobile number or email address without setting them up first. Recipients live in your Address Book or are passed in with each message. For Address Book setup see
Adding Address Book Contacts.
⚠️ Admin access required
Only an Account-level login can create or edit Admin Users. Lower tier users can only create users in their SubAccount and/or Department (depending on access rights).
🚀 Before you start
Decide what this User will do:
- Just send messages? Create the User with sending only.
- Log into the dashboard too? Enable Dashboard access.
- Send via API? Enable API access and generate credentials.
You can change any of this later. For a field-by-field breakdown of every option, see User Configuration Fields.
1. Create a User
Each User is one authorised sender email address. Here's how to add one.
| 1. Log in to my.tnz.co.nz as an Account-level user. |
| 2. Select Users from the menu. |
| 3. Click the Create button. |
4. In User Email Address, enter the address you're authorising (for example, accounts@yourcompany.co.nz). |
| 5. Set SubAccount, Department, and other defaults if needed. See the User Configuration Fields reference. |
| 6. If this User also needs to log into the dashboard, switch to the Dashboard tab. See Task 2. |
| 7. Click Save. |
💡 Tip: wildcard a whole domain
Set Domain Account to Yes and enter just yourcompany.co.nz in User Email Address. Any address at that domain will then be authorised to send. This applies for Email-to-SMS, Email-to-Voice, Email-to-Fax, and Email-to-WhatsApp only (not Dashboard or API access).
2. Grant dashboard access to an existing User
If a User needs to log into my.tnz.co.nz, give them dashboard access.
| 1. Select Users from the menu. |
| 2. Click the User in the list. |
| 3. Switch to the Dashboard tab. |
| 4. Set Enable Dashboard Access to Yes and choose a Login Level (see the Login Level reference below). |
| 5. Set Send Welcome Email to Yes if you'd like TNZ to email the User their login details automatically. |
| 6. Enter a secure password or use the Generate button to create one. |
| 7. Click Update. |
For every field on the Dashboard tab (MFA, default page, password reset, etc.), see User Configuration Fields (Dashboard tab).
3. Enable API access for an existing User
If a User will send via API, this is where you generate their credentials.
For API-specific options see the Managing API Users, APIKeys and Authorization guide.
| 1. Select Users from the menu. |
| 2. Click on the User in the list. |
| 3. Switch to the API tab. |
| 4. Set Enable API to Yes. |
| 5. Enable the Auth Token or Sender/API key (depending on your requirements) |
| 6. Toggle the Reporting options to suit, e.g. send an email notification, or fire webhooks. If using Webhooks, set a Webhook Callback URL to be used as a default. |
| 7. Click Update. |
🔐 API credentials are sensitive
Treat them like passwords and rotate them if a developer leaves the team.
For every field on the API tab (webhook URL, callback format, per-channel reporting), see User Configuration Fields (API tab).
4. Edit, deactivate, or delete a User
Plans change and staff move on. Two ways to handle that:
💤 Deactivate (recommended)
Keep the User record and their reporting history. Open the User, set User Status to Inactive, and click Update. They can no longer send, and you can reactivate any time.
🗑️ Delete (permanent)
Remove the record entirely. Open the User and click Delete. Delete is permanent. There's no undo. Reporting history is retained against the original ID, but the User won't appear in lists.
If you're unsure, deactivate. It's the safer option and it covers the most common case (a team member leaves but you might want the record back later).
To edit a User, follow the same flow used in Tasks 2 and 3: Users > click the User, then change settings on the relevant tab and click Update.
5. Login Level reference
Login Levels control what each User can see and edit in the dashboard. They follow the same hierarchy used for SubAccounts and Departments.
| Login Level |
Description |
| Account |
Admin login. Can view and edit all Users, messages, and contacts on the account. |
| SubAccount |
Second tier. Can view and edit information owned by their SubAccount and the levels below it. |
| Department |
Third tier. Can view and edit information owned by their Department and associated Users. |
| End User |
Lowest tier. Can view and edit information owned by their login only. |
6. Troubleshooting
The User has been added but they can't send.
Check User Status is Active. If you've wildcarded a domain, confirm Domain Account is set to Yes and the User Email Address field contains the domain only (for example, yourcompany.co.nz), not a full address.
|
The Welcome Email didn't arrive.
Confirm Enable Dashboard Access is Yes and that Send Welcome Email was ticked when you saved. The email is sent from a TNZ system address. To resend, edit the User, disable their dashboard access, Save, re-enable it again, tick Send Welcome Email again, and click Update.
|
The wildcard domain isn't working.
The most common cause is that User Email Address contains user@domain.com instead of just domain.com. Remove the user@ portion (including the @ symbol) and click Update.
|
The wrong User got deleted.
Delete is permanent. Recreate the record and reapply the settings. Reporting history is retained under the original User ID. If the User had API credentials, the new record will be issued a new APIKey, so any integrations referencing the old one will need to be updated.
|
"User not authorised" errors when sending via Email-to-SMS.
The sending address isn't authorised. Either add it as a User, or set up a wildcard Domain Account User covering its domain.
|
Still stuck? Find more answers in the TNZ Help Centre, or get in touch with our NZ-based team.
Contact TNZ support →