Most teams do not want one person to be the only one who sees invoices or service emails. MdmHost lets you add contacts to your account: people who receive the billing, support or service emails you choose. This guide shows how to add one, how contacts differ from people who can sign in, and how to keep access limited.
Before you start
- You are signed in to the Dashboard as the account owner.
- The contact's name and email address. Their company, phone and address are optional but useful for billing contacts.
- A clear idea of what this person needs: invoices only, service notices, support replies, or a mix.
Contacts vs people who can sign in
There are two different ways to involve another person:
- Contacts receive emails about your account. They do not get a password and cannot sign in to the Dashboard just by being a contact. This suits an accountant who needs invoices, or a colleague who should see service notices.
- Users with access can sign in to the account. This is managed separately, under Security, and suits someone who has to manage servers or pay invoices themselves.
Start with a contact. Give sign-in access only if the person really needs to act in the Dashboard.
Warning: Never share your own password with a colleague. Shared passwords cannot be revoked for one person, and every action looks as if you did it.
Add a contact
- Open the account area in the Dashboard and choose Contacts. This page lists the people who receive billing, support or service emails for your account.
- Click Add contact.
- Fill in the details:
- First name and Last name.
- Email: the address they will receive messages at.
- Company, Phone and address fields, if useful. They are optional for most contacts.
- Under Emails this contact receives, tick only the types this person needs. For example, an accountant usually needs invoice and billing emails, not technical service notices.
- Click Save contact.
The contact now appears in the list with the email types they receive.
Keep access limited
Give each person the smallest amount of access that lets them do their job:
- Accountant or finance team: a contact who receives billing emails.
- Developer who manages a server: server access is usually best handled on the server itself. Create a separate login for them on the server, rather than sharing the main one.
- Office manager who pays invoices: a contact for billing emails, or sign-in access if they must pay in the Dashboard.
Review the list every few months. When someone leaves the team or a supplier relationship ends, remove them the same day.
Edit or remove a contact
- Go to Contacts in the account area.
- Open the contact to change their details or the emails they receive, then save.
- To remove someone, use Delete next to their entry and confirm.
Note: Removing a contact stops future emails to them. It does not remove any server logins you created for that person. Remove those on the server as well.
Check it works
- The contact appears in the Contacts list with the right email address.
- The email types ticked for them match what they need.
- Ask the contact to watch for the next relevant email, such as the next invoice, and to add the MdmHost sender to their safe senders list.
Troubleshooting
- The contact does not receive emails: check the email address for typos, confirm the right email types are ticked, and ask them to look in spam folders.
- The contact tries to sign in and cannot: that is expected. Contacts receive emails only. Give sign-in access under Security if they truly need it.
- You cannot save the contact: a required field is missing or an email address is already used. Check the message next to the field.
- A former colleague still receives emails: delete their contact entry, then check Security for any sign-in access they still have.
Next steps
- Review who can sign in: Secure your MdmHost account.
- Keep your own details current: Update your profile and contact details.
- Give a colleague their own Windows login: Create a Windows user with RDP access.
- On Linux, give each person their own account: Create a sudo user on Linux.
