Those requiring access to Company Settings must be a user and assigned to Company Settings role. The Kontakt.io platform uses role-based permissions to manage user access — each role provides a predefined set of permissions that control what a user can and cannot do within an app. Users and their assigned roles are managed in from the Users app. It's recommended that a minimum of two users are assigned to the Company Settings Administrator role.
Important
Only those assigned to the User Management Administrator role have permission to manage users and their assigned roles.
Topics include:
For access to Company Settings, a user is required to be assigned to a role.
The following describes each role and the permissions it provides.
-
Administrator: All permissions.
Role is ideal for those responsible for entity management and room management.
-
User: Permission to only Webhooks. They do not have permission to view or access any other menus within Company Settings.
Role is ideal for those responsible for managing third-party integrations.
|
Permission |
Administrator |
User |
|---|---|---|
|
Entity Types Create, view, edit, delete |
Yes |
No |
|
Entities Create, view, edit, delete |
Yes |
No |
|
Room Types Create, view, edit, delete |
Yes |
No |
|
Room Matching View, edit |
Yes |
No |
|
Webhooks Create, view, edit, delete |
Yes |
Yes |
Note
Each Kio App also has an Administrator role designed for users responsible for entity management within with the app. The app Administrator does have limited entity management permissions within the Kio App, such as they cannot delete entities or edit Entity IDs, and have view-only access to Room Types and Room Matching.
In contrast, the Company Settings Administrator role is a power-user role with permissions to all entity and room management features. This role should be assigned only to those responsible for entity and room management shared across the Kio Apps.
From the Users Management menu, each user has a unique profile that includes the following details.
-
First Name, Last Name: displayed throughout the Kontakt.io platform.
-
Email: if their Sign-in Method is set to Password, this is their user name used to sign in to the Kontakt.io platform.
-
Unique Ext ID: a secondary unique identifier; maximum of 35 characters. For example, it may be their unique employee ID within your HR management system.
This ID is required to access the iOS Kio Nurse Assistant mobile app for Asset Tracking and Hand Hygiene.
-
Sign-in Method: identifies the user's sign in and authentication method, either SSO, SSO_RA, or Password.
-
Roles for Apps: identifies the user's assigned role within each app within the Kontakt.io platform.
-
Campus: identifies the user's access to all Campuses (default) or specific Campuses (advanced configuration).
When Allow access to all campuses is disabled, the user must be assigned to one or, optionally, multiple campuses. Each assigned campus grants the user access to the campus, its buildings, and the building floors across the entire Kontakt.io platform. To set this advanced configuration, the account requires "campus-level user access" that is managed by Kontatk.io. If you need enable or verify this advanced configuration, submit a support request.
-
From your Kontakt.io Launchpad, select Users.
-
From the upper-right corner, select Add User.
-
Enter their user-specific settings:
First Name, Last Name, Email
Unique Ext. ID: a secondary unique identifier; maximum of 35 characters. For example, it may be their unique employee ID within your HR management system.
Sign-in method two options:
Password (default value): select when your organization's Kontakt.io account is not integrated with Single sign-on (SSO). Users are required to sign in with their email and password.
SSO_RA: select when your organization's Kontakt.io account is integrated with Single sign-on (SSO). The user will sign in and authenticate with their SSO credentials.
-
Once complete, select Add User.
A user set with the Password sign-in method receives an activation email to set their password.
-
To assign their app roles, from the list of users > select their Name.
-
From the Kio Apps section, assign their roles to the apps they require access to.
The apps available are only those activated in your organization's Kontakt.io account.
If a user isn’t assigned a role for an app, that app won’t appear on their Kontakt.io Launchpad.
-
When done, select Save.
A user's assigned role determines their access and permissions within each of the apps. If a user is not assigned to a role within an app, the app is not available from their Kontakt.io Launchpad.
-
From your Kontakt.io Launchpad, select Users.
-
From the list of users, locate the user > select their Name.
-
From the Roles for Apps section, select Edit.
-
From an app, update their assigned role > select Save.
For users with a Sign-in Method of Password, you have two options to remove their access to your organization's Kontakt.io account.
-
Disable a user: When you disable a user, their sign-in access is temporarily removed. This action performed from their user profile and can be reversed at any time.
-
Remove a user: When you remove a user, their user profile is permanently deleted. Although the profile is deleted, all historical user activity within your Kontakt.io account is retained. This action is commonly used when a user has left your organization. This action is performed from the list view within Users Management.