Access Methods
Hybo allows you to choose between three access methods, depending on the platform used by the organization and its specific needs:
Corporate email and password: Users sign up using their corporate email to create a Hybo account; during this process, they set a password specifically for Hybo.
âSingle Sign-On with Microsoft Office 365: Users access Hybo using their corporate Microsoft credentials.
âSingle Sign-On with Google Workspace: Users access Hybo using their corporate Google credentials.
Single Sign-On (SSO) methods eliminate the need for users to manage a separate account for Hybo, offering greater convenience and security, for example, by allowing the use of multi-factor authentication (MFA).
Regardless of the access method, user registration in Hybo is self-service; it does not require an invitation or any manual intervention from administrators. For a clearer understanding of how user registration works with each method, please refer to How to Access and Start Using Hybo.
Corporate Email Validation
Regardless of the access method, Hybo ensures that only users with a corporate email address can access the platform. During the environment setup, simply provide the Hybo Support team with the authorized domains and/or subdomains, for example: @hybo.com, @hybo.app, and @external.hybo.app.
Once the platform is set up, you may request to expand or restrict the list of permitted domains at any time.
Permission Management Models
Regardless of the access method, Hybo allows you to manage users and their permissions entirely within the platform:
Groups: These bring together users who share the same permissions. Each group can have different scopes enabled and be associated with multiple roles.
âScopes: These define where a groupâs permissions apply, for instance, to specific offices, buildings, or zones.
âRoles: These determine which features users in a group can access and what actions they are permitted to perform.
Additionally, in environments using Microsoft Office 365, Hybo also allows for the management of groups and their members directly within Microsoft Entra ID (formerly Azure Active Directory).
| Hybo groups | Entra ID groups |
Acces with Microsoft Office 365 | â | â |
Acces with Google Workspace | â | â |
Acces with email and password | â | â |
Integration with Entra ID
This integration allows you to manage groups and members directly from Entra ID, eliminating the need to perform these tasks within the Hybo admin panel.
| Hybo groups | Entra ID groups |
Creating groups | In Hybo | In Entra ID |
Adding or removing members | In Hybo | In Entra ID |
Configuring scopes | In Hybo | In Hybo |
Assigning roles | In Hybo | In Hybo |
What Are the Benefits?
Centralized management: The IT team can grant or revoke access to Hybo via Entra ID, using the same processes already in place for managing employee onboarding and offboarding.
Always up-to-date permissions: Changes made to Entra ID groups are immediately reflected in Hybo permissions. If a user is removed from these groups, their access is automatically disabled the next time they attempt to log in.
âPermissions configured from the first login: You can assign a user to multiple groups before they log in to Hybo for the first time. In contrast, with internal Hybo groups, you can only define a single default group, which cannot be changed until the user logs in for the first time.
âPeriodic user deactivation: Hybo offers a service that automatically deactivates users who are no longer members of any Entra ID group, without waiting for them to attempt to log in. This reduces administrative overhead and frees up licenses for other employees to use. Learn more in User Deactivation Integration.
Integration requirements
Integrating with Entra ID requires:
Registering an application in Microsoft Entra ID, and
âGranting it the necessary Microsoft Graph permissions to query users, groups, and group memberships:
âUser.Read: Allows reading the profile of the signed-in user.Directory.Read.All: Allows reading directory information.Group.Read.All: Allows reading groups and their properties.GroupMember.Read.All: Read group members.
