Enable HyperConnect access for employees
Each employee who needs to use HyperConnect must have the Connect Access Enable permission assigned to their security role. Without this permission, employees cannot open HyperConnect from the Zenoti navigation menu.
This article explains how to grant access per role and per channel. Because a user with several roles is the most common reason a correct-looking grant has no effect, verify the permission on every role the employee holds.
On this page
Before you begin
Permission: Security role management (under Security) β Required to assign permissions to security roles.
HyperConnect must be provisioned for at least one center in your organization.
Identify the security roles that need HyperConnect access (for example, front desk, manager, or provider roles).
Grant HyperConnect access on the roles people already hold. HyperConnect permissions are set per role and per channel, so adding them to an existing front-desk or manager role is enough. Do not assign a provider job role to give someone HyperConnect access. A job designation configured as a service-provider role also makes that employee a bookable provider, so they appear as a column on the appointment book and can be selected when booking a guest. See Create and manage jobs.
If a messaging or voice surface disappears across an entire organization while individual permissions appear intact, check the organization's HyperConnect entitlement first. A lapse in the add-on presents as a permission-style error message, which makes the permission trail a false lead β stop auditing roles and contact your Zenoti account representative to verify provisioning status.
Steps
Grant HyperConnect access to a security role
Channel access is granted per role and per channel. A user who holds several roles must have the permission enabled on every role they hold β a single missing channel on any one role is why one conversation type can be absent while the others work.
- At the organization level, navigate to Configuration > Security > Security Roles.
- Select the security role you want to grant HyperConnect access to.
- In the role's permissions list, search for Zenoti HyperConnect or scroll to locate it.
- Enable the Connect Access Enable checkbox under Zenoti HyperConnect.
- Enable the channel-specific permissions the role requires. Channel permissions are separate from the base access permission β a user can have base access but be missing a specific channel. Key channel permissions to verify:
- Email β Required for the Email channel to appear in conversations. When absent, the Email icon is missing from the conversation view while other channels remain visible.
- Enable Incoming Calls / Enable Outgoing Calls β Required for voice calls.
- Messages (Send) β Required to send messages, and required at the center for the employee to receive push notifications for that center's incoming messages. Enable any other feature-specific permissions the role requires (for example, tags, saved responses, or reporting).
- Click Save.
- Repeat steps 2β6 for every other security role the employee holds.
All employees assigned to the updated security roles can now access HyperConnect from the Zenoti navigation menu.
Tip: When a specific channel (for example, Email) is missing from a user's HyperConnect conversation view while other channels work, the cause is almost always a missing channel permission on one of the user's roles β not a guest data issue or credit balance problem. Check the Email permission on every role the user holds before investigating guest-level settings.
Tip: Repeat these steps for each security role that needs HyperConnect access. You do not need to update individual employee records.
Verify employee access
After you update the security role, verify that employees can access HyperConnect.
- Ask an employee with the updated role to log in to Zenoti.
- Confirm that HyperConnect appears in the navigation menu.
- Confirm that the employee can open HyperConnect and see the expected interface.
Note: If HyperConnect does not appear after updating the security role, confirm that HyperConnect is provisioned and enabled for the employee's center. The employee may need to log out and log back in for the permission change to take effect.
Configure employee-level settings
After an employee has access to HyperConnect, you can optionally configure their individual settings, such as notification preferences and default views.
- Open HyperConnect.
- Navigate to Settings.
- Select the employee whose settings you want to configure.
- Adjust the employee's preferences as needed.
- Click Save.
Why access and mobile alerts are granted differently
Access and push notifications are not decided the same way, and this is the most common reason push stops for a whole center while everything else looks correct.
Access is honored from any role that grants it β a role that applies across the whole organization, a role that applies across a zone, a role held at the center, or access through deputation. Any one of them opens HyperConnect and the full inbox.
Push notifications for incoming messages are stricter. To receive them for a center, the employee must hold a role at that center that carries both the HyperConnect access permission and the messaging Send permission. A role that grants access organization-wide or across a zone is enough to open the inbox but does not qualify the employee for push at that center.
So an employee can have complete, working access to a center's conversations and silently receive no alerts for them. The symptom is push stopping for one center with access intact β which looks like a device or app fault, and is not. Before reinstalling the app or checking operating-system notification permissions, confirm the employee holds a role at that center with both permissions enabled.
Two other conditions must also hold: the employee's Push Notification preference must be on in Configure user settings, and the employee's record must be within its employment dates β a start date in the future, or a last working date already past, stops alerts.