Contacts and Sub-Accounts

The person who pays is rarely the only person who needs to see an invoice, open a ticket, or reboot a server. MyNobull has two features for that: contacts, who receive copies of chosen emails, and sub-accounts, who get their own login with only the permissions you grant. Neither requires sharing your password, which is the entire point.

Contacts#

A contact is an email recipient attached to your account. Use it for accounts payable (invoice emails), an on-call mailbox (support ticket emails), or a colleague who should see product notices.

1. Open Account, then Contacts/Sub-Accounts in MyNobull, and choose Add New Contact.
2. Enter their details and tick the email categories they should receive: General, Product, Domain, Invoice, and Support.
3. Save. They start receiving copies immediately; you keep receiving yours.

Sub-accounts#

Ticking Activate Sub-Account on a contact gives that person their own MyNobull login (their email plus a password they choose) restricted to the permissions you select:

• View Products & Services, and optionally Manage Products (upgrades, cancellation requests, panel logins).
• View Domains and Manage Domain Settings.
• View & Pay Invoices, and Manage Billing (payment methods).
• View & Open Support Tickets; optionally only their own tickets.
• Modify Master Account Profile, which you should almost never grant.

Sub-account holders log in at the normal MyNobull login with their own address; if they have several accounts, MyNobull asks which to open. Change permissions or remove a sub-account at any time from the same page; access ends immediately.

Sensible presets#

Accounts payable

Contact with Invoice emails, or a sub-account with View & Pay Invoices only.

Developer or ops colleague

Sub-account with View Products & Services, Manage Products, and support ticket permissions. Pair it with their own login on the cloud portal or as a game panel sub-user for hands-on work.

Business partner

Sub-account with everything except Modify Master Account Profile.

Security notes#

• Sub-account holders should enable two-factor authentication on their own login just as you do on yours.
• When someone leaves, remove the sub-account and change any shared credentials on servers they touched. See Recover from a Compromised Server for the rotation list if the departure was not friendly.
• Support verifies identity against the account holder and authorised contacts. Keeping this list current is what lets a colleague get help quickly when you are on holiday.