Contacts vs User Management Print

  • 0

Contacts and User Management are two different ways of managing access and permissions. They often get mixed up, but they serve different purposes. Here’s the breakdown:

Feature Contacts User Management
Login Access ❌ No separate login (shares primary client login only) ✅ Each user has their own unique login credentials
Purpose Email notifications & limited permissions Secure multi-user access with role-based permissions
Best For Accountants, billing staff, or IT staff who only need emails Teams, agencies, MSPs, or multiple staff needing portal access
Can Access Client Area? ❌ Not independently (unless using main login) ✅ Yes, with their own login
Permissions Limited: ticket management, email preferences, etc. Granular: full access, billing-only, support-only, etc.
Multi-Account Access ❌ Tied to a single client account ✅ One user can access multiple client accounts
Audit Trail ❌ Actions are attributed to the main client ✅ Actions tied to the specific user (better accountability)
Setup Quick — just add a contact under the client profile Requires invitation + user acceptance
Notifications ✅ Can select which emails (invoices, tickets, domains, etc.) they receive ✅ Users get their own notifications based on permissions
Security ⚠️ Weaker (shared login risk) ✅ Stronger (unique logins, MFA possible)

 

1. Contacts

  • Purpose: Originally designed to let a main account holder (the "Client") add other people to receive communications.

  • Access: Contacts do not have a separate login to the billing portal. They exist under the primary client account.

  • Usage:

    • Can receive selected emails (invoices, support ticket updates, domain notices, etc.).

    • Can be given limited permissions like opening/viewing support tickets.

  • Best for:

    • Billing contacts (e.g., accountant gets invoices).

    • Technical contacts (e.g., sysadmin gets support ticket notifications).

    • But they always operate under the primary login.


2. User Management

  • Purpose: A more modern system to allow multiple unique logins (Users) to access one or more client accounts.

  • Access: Each User has their own credentials.

  • Usage:

    • A User can be linked to multiple client accounts (great for resellers, agencies, IT managers handling multiple companies).

    • Each User has assigned permissions (full admin, billing only, support only, etc.).

    • Users can be invited/removed without affecting the main client account itself.

  • Best for:

    • Teams or organizations where multiple people need their own login.

    • MSPs or agencies managing hosting for multiple clients.

    • Situations requiring audit trails (you know exactly which user logged in and did what).


Advantages of Each

Contacts

✅ Simple to set up
✅ Good for “email-only” notifications
✅ Useful when one person manages everything, but wants others copied in

⚠️ Limitation: No independent login, so not ideal for shared access


User Management

✅ Separate logins for each person (better security & auditing)
✅ One User can access multiple client accounts (no more juggling logins)
✅ Permissions are clearer and more granular
✅ Easier to add/remove people without exposing the main account credentials

⚠️ Slightly more setup overhead than just adding a contact


In Practice

  • Use Contacts if you just want someone copied on invoices or ticket emails.

  • Use User Management if you need multiple people to actually log in and interact with the system.


Was this answer helpful?

« Back