SoniCloud Users, Groups, Permissions, and SSO
SoniCloud implements a fine-grained, flexible permission structure to ensure that users can only see what they need to see and access what they need to access.
This ensures your SoniCloud system stays in a regulatory compliant setup with no upkeep.
It’s important to understand how this system is implemented as you consider the SoniCloud system.
SoniCloud users have the ability to view one (or more) sites, depending upon the size of their organization and what their permissions include
SoniCloud users login via their email address and are able to have site-specific:
SoniCloud provides the option for customers to use the following password restrictions:
Each SoniCloud user can belong to one or more groups.
These groups are assigned to a Zone, which gives users the ability to view points in that zone.
In the example above, there are two zones:
A user that belongs to the Pharmacy Managers group would only be able to see the points in the Pharmacy Zone.
A user that belongs to the Dietary Managers group would only be able to see the points in the Dietary Zone.
A User that belongs to the Facilities group, however, would be able to see both the Pharmacy Zone and the Dietary Zone.
This ensures each user only sees information relevant to them.
SoniCloud permission levels allow for fine-grained capabilities on a per-site basis.
If a user has access to multiple sites, they can have different permissions levels for each site – for instance, a user may need to have Admin permissions at a central location, but only View permissions at satellite locations.
Sonicu recommends limiting Manager and Admin permission levels to only critical teammates to ensure that changes aren’t made that unintentionally affect others in the system.
SoniCloud offers Single Sign-On (SSO) support via the Security Markup Language (SAML), the industry standard for logging in users to multiple applications via a single authentication method.
SoniCloud leverages AWS Cognito as the SAML federation provider.
This allows a customer to pair with SoniCloud and leverage SAML and their internal Active Directory (AD) implementation to provide SSO for SoniCloud.
Sonicu recommends SSO be enabled for all customers, as this allows customer IT to enforce desired security settings, including
Enabling SSO starts with an exchange of technical contact information between Sonicu and the customer.
The customer will be asked to provide the following information:
Sonicu will provide the following information:
After this information is exchanged, a 30 minute meeting will be scheduled between Sonicu IT and customer IT to enable SSO and validate the SSO connection.
After this, all existing user accounts for the customer will be swapped to SSO.
SoniCloud’s SSO implementation is limited to authentication – that is, SSO is utilized to determine if a user has met the requirements to be logged in.
SoniCloud does not utilize SSO for authorization – that is, to determine which groups a user should be in (and, therefore, which points of monitoring they have access to).
User authorization will still be handled by the permission levels and groups described earlier in this document.