1. Open Clients > Manage Clients > Client Profile > Contacts. Confirm the parent account and review existing contacts for duplicates.
2. Use Add contact for a new contact. Where the person already has a registered address, use the supported invitation workflow for a guest profile instead of creating a conflicting identity.
3. Enter the person's correct details and language. Select the required permissions for billing, support and service access.
4. Separate notification permissions from action permissions. A contact who receives invoices may not need to edit payment details, place orders or accept contracts.
5. Restrict ticket-department and per-service access where supported and appropriate. Avoid granting full service or domain control solely so someone can view one technical ticket.
6. Complete the approved invitation or registration process and check the resulting status. A sent invitation is not the same as an active, accepted contact.
7. Verify a representative allowed action using the contact's normal access. Confirm that unrelated financial or service actions are unavailable.

When the customer's personnel change, review contact status, permissions and notification destinations. Remove access through the supported account-management process and check any separately issued API or infrastructure credentials.

Keep the authorisation record with the customer request. A support email's display name or signature alone is not sufficient reason to grant broader account control.

A customer authorises its finance colleague to receive invoices and review billing without administering hosting or domains. Open Clients > Manage Clients > Client Profile > Contacts for that customer.

1. Check for an existing contact or registered guest identity.
2. Add or invite the colleague using the correct business email address.
3. Select the billing notification and account permissions needed for the authorised work.
4. Leave unrelated service, domain and support access unselected unless it was requested.
5. Complete the invitation process and have the colleague verify a representative permitted billing action.

Expected result: the finance contact can perform the agreed task under their own access. Receiving invoice messages and having permission to change account settings remain separate choices.

• Organize HostBill ticket status assignment and escalation
• Configure HostBill contract generation for orders
• Apply client-specific HostBill settings and automation overrides
• Verify account authority before changing hosting access

• HostBill client contacts
• HostBill support ticket management
• HostBill message templates

• Manage HostBill client contacts and access permissions