Skip to main content
In this video, I’m going to demonstrate how to edit and create new User Roles, as well as how to add New Users to the KIBO Business Admin UI. In this video, I’m going to demonstrate how to edit and create new User Roles, as well as how to add New Users to the KIBO Business Admin UI. First, we’ll look at how to edit and create new User Roles. In the left menu, on the “System” tab, click “Permissions”, then click Roles. First, we’ll look at how to edit and create new User Roles. In the left menu, on the “System” tab, click “Permissions”, then click Roles. This is the Roles menu. It lists all User Roles that have been created in this tenant. This is the Roles menu. It lists all User Roles that have been created in this tenant. The KIBO Admin UI comes with several “System Roles” out-of-the-box. “System Roles” cannot be customized. However, they can be duplicated as “Custom Roles” and then configured as needed. The kibo admin UI comes with several system roles out of the box. System roles cannot be customized, however, they can be duplicated as custom roles and then configured as needed. To view a role, you can click the “Ellipses” for that Role and then click “View”. Alternatively, you can just click directly on the Role. To view a role, you can click the “Ellipses” for that Role and then click “View”. Alternatively, you can just click directly on the Role. This opens a modal window for the selected Role to view the “Permissions”, or what KIBO calls “Behaviors”, associated with that Role. Again, “System Roles” cannot be edited, but they can be duplicated as “Custom Roles”, which can be configured as needed. This opens a modal window for the selected Role to view the “Permissions”, or what KIBO calls “Behaviors”, associated with that Role. Again, “System Roles” cannot be edited, but they can be duplicated as “Custom Roles”, which can be configured as needed. To duplicate a “System Role”, we’ll first locate the role we want to duplicate, click the “Ellipses” for that role, and then click “Duplicate”. To duplicate a “System Role”, we’ll first locate the role we want to duplicate, click the “Ellipses” for that role, and then click “Duplicate”. This will open up a modal window where we can further configure the new duplicated role. We’ll need to give the new role a “Name”, and then select a “Behavior Category” that we want to edit. In this example, we’ll use “Product”. This will open up a modal window where we can further configure the new duplicated role. We’ll need to give the new role a “Name”, and then select a “Behavior Category” that we want to edit. In this example, we’ll use “Product”. Depending on the “System Role” that has been duplicated, there may be “Behaviors” that are already pre-selected. We can simply uncheck any of the pre-selected “Behaviors” we do not want to include with this new Role. Depending on the “System Role” that has been duplicated, there may be “Behaviors” that are already pre-selected. We can simply uncheck any of the pre-selected “Behaviors” we do not want to include with this new Role. As we update the “Behaviors” that we want to include, the “Selected Behavior” column will automatically update so we can track all of the “Permissions” that will be included in this new Role. These “Behaviors” are granular and generally relate to create, read, update, and delete permissions for all aspects of a “Behavior Category” As we update the “Behaviors” that we want to include, the “Selected Behavior” column will automatically update so we can track all of the “Permissions” that will be included in this new Role. These “Behaviors” are granular and generally relate to create, read, update, and delete permissions for all aspects of a “Behavior Category” When we have added all of the “Behaviors” we want to include with this new Role, we’ll click “Save”. When we have added all of the “Behaviors” we want to include with this new Role, we’ll click “Save”. To create a brand new “Custom Role”, we’ll click the “Create New Role” button on the top right. To create a brand new “Custom Role”, we’ll click the “Create New Role” button on the top right. Similar to the process of duplicating a Role, we’ll input a new “Name”, select a “Behavior Category” to edit, and then we’ll select the “Behaviors” we want this role to have. In this example, we’ll add from the “Order” category. This time there will not be any pre-selected “Behaviors”. Similar to the process of duplicating a Role, we’ll input a new “Name”, select a “Behavior Category” to edit, and then we’ll select the “Behaviors” we want this role to have. In this example, we’ll add from the “Order” category. This time there will not be any pre-selected “Behaviors”. Again, as we update the “Behaviors” that we want to include, the “Selected Behavior” column will automatically update so we can track all of the “Permissions” that will be included in this new Role. Again, as we update the “Behaviors” that we want to include, the “Selected Behavior” column will automatically update so we can track all of the “Permissions” that will be included in this new Role. When we have added all of the “Behaviors” we want to include with this new Role, we’ll click “Save”. When we have added all of the “Behaviors” we want to include with this new Role, we’ll click “Save”. Now that we know how granular User Roles and Permissions are and how they can created and managed, let’s look at how to add a New User to the Sandbox environment. To do that, in the left menu, still on the “SYSTEM” tab, we’ll click “Permissions” again, and then “Users”. Now that we know how granular user roles and permissions are and how they can create it and managed. Let’s look at how to add a new user to the sandbox environment to do that. In the left menu, still on the system, tab will click permissions again and then users. This is the Users Menu. This will list all users that have access to this tenant, and the Roles assigned to them. This is the Users Menu. This will list all users that have access to this tenant, and the Roles assigned to them. If we need to locate a specific User, we can use the Search and Advanced Filtering bar at the top of the page. If we need to locate a specific User, we can use the Search and Advanced Filtering bar at the top of the page. If the User has “Multiple” Roles assigned to them, we can click the dropdown next to the Users Email slash Username to see all Roles. If the User has “Multiple” Roles assigned to them, we can click the dropdown next to the Users Email slash Username to see all Roles. Alternatively, to expand all Users and view their User Roles, click the “Ellipses” on the far top right, next to the “Add User” button, and then click “Expand All”. Conversely, we can also “Collapse All” Users from here. Alternatively, to expand all Users and view their User Roles, click the “Ellipses” on the far top right, next to the “Add User” button, and then click “Expand All”. Conversely, we can also “Collapse All” Users from here. KIBO tracks the login Activity and Status for each User, and provides the “Last Login” date and time on the Users Menu. KIBO tracks the login Activity and Status for each User, and provides the “Last Login” date and time on the Users Menu. To “Delete” a user, click the “Ellipses” on the far right of the individual user, then click “Delete User”. We can also open the “Edit” window from here to edit the user details, or we can click directly on the user to “Edit”. To “Delete” a user, click the “Ellipses” on the far right of the individual user, then click “Delete User”. We can also open the “Edit” window from here to edit the user details, or we can click directly on the user to “Edit”. To add a new user to the tenant, click the “Add User” button on the top right. To add a new user to the tenant, click the “Add User” button on the top right. Input the Users “Email” address here. This will also be set as their initial “Username” for login purposes. Input the Users “Email” address here. This will also be set as their initial “Username” for login purposes. Select a pre-defined role for the new user by selecting the checkbox to the left of the role. We can add as many Roles as the User may need. For example, maybe the User is a Store Manager, which gives them limited access to the UI, but we also want them to have access to the Reporting menu. We can add both Roles here. Select a pre-defined role for the new user by selecting the checkbox to the left of the role. We can add as many Roles as the User may need. For example, maybe the User is a Store Manager, which gives them limited access to the UI, but we also want them to have access to the Reporting menu. We can add both Roles here. Once all Roles have been added, click “Invite User”. This will send the new user an email message, notifying them of the new access and providing them a link to complete their new user profile. Once all roles have been added, click. Invite a user. This will send the new user an email message. Notifying them of the new access and providing them a link to complete their new user profile. When a new user is invited into the KIBO Commerce platform, they will receive an email similar to the one shown here. Important note - since this is a “system-generated” email, it can sometimes be filtered out as Spam. When a new user is invited into the KIBO Commerce platform, they will receive an email similar to the one shown here. Important note - since this is a “system-generated” email, it can sometimes be filtered out as Spam. KIBO’s Admin UI can limit access based on a Users Role, and the Permissions associated with that Role. For example, if a user had a “Fulfiller” role in a store or warehouse, their access within the UI could be limited to only those menus that are essential for that role, as shown here. Keep those admin. UI can limit access based on a user’s role, and the permissions associated with that role. For example, if a user had a fulfill a role in a store or Warehouse their access within the UI could be limited to only those menus that are essential for that role as shown here. Using the same example, there would be no “SYSTEM” menus that a “Fulfiller” role would need to access, so those have all been disabled. Using the same example, there would be no “SYSTEM” menus that a “Fulfiller” role would need to access, so those have all been disabled.

Want to learn more?

User Roles

Learn more about this topic

Administration

Learn more about this topic