User Groups in InSkill

User groups are a way of creating sub-domains within your InSkill account. The primary goal is for delegated administration of a business unit or division. Say you have different groups for cars, trucks and SUVs. Each one can contain its products, users and customers. A group administrator has admin rights within that group. All of the roles like Author or helpdesk user are valid within that group. And the activities in history or userlog are per group.

All User Groups are within a single InSkill account, so an account administrator can manage all the users, customers and products. SSO can apply to all logins as well.

User Groups are hierarchical so a group for Support can have subgroups for each region, and the group administrator for Support can manage all of their users and subgroups. User Groups can contain products, but they can also just inherit their parent's products. For regions that all use the same products this makes it easier to manage.

Support
--- Support NA
--- Support EU

In this structure, if Henry is in Support EU, he is also in Support. His activity will be in the history of Support EU, and also in Support and of course in the overall account.

Users can be members of multiple user groups, which means they can see the products in those groups. There is just one Role, so users have the same permissions across all products, users etc.

An account has an API key, and each user group also has one that has a limited scope. So APIs can be used consistently.

User Groups guide

There is an Account Administrator role that can create user groups to begin. Under Admin go to Groups tab and create the main groups. For an existing account, each group can add products and users and customers to get started. The minimum needed is a group with a member who has Group Administrator role. They can then create users and products that live within their group.

A group has a name and optional description, and an API key used for automation. The key can be rotated (replaced with a new key) when needed. The group's products, users and customers can be managed on the group page. Users and Customers can also be filtered and groups set on their pages.

A member of a group will have a filtered view of products. If they create new product, it will be in their group so it is visible to them. An author in multiple groups can select which group to include the product. A user cannot create a product that is invisible to them.

Likewise creating users or customers, a group member will automatically have them in their group.

Intelligence page has a dropdown with the visible groups. Selecting a group will filter to activity by members of that group. Userlog is the same.
An action is related to a group based on the user's membership at the time. If Tom is in support group and runs a task, that will show up in the userlog, etc. even if Tom is no longer in that group. Also adding a user to a group will not bring along all their previous actions.

The same applies to the APIs, if using a group apikey and query users, diagnosticsessions, or gpt, it will only return those actions related to the group.

details

Editing group members, the search allows multiples, so paste a list of emails to add to the group and all will be shown. Then select them and Add.

When products are added to a group, their components are also added so they are self-consistent.

Changes

Role Administrator is now Account Administrator
A new role Group Administrator gives full capabilities but limited to the groups they are members of. This is the way to do delegated administration. This role can manage subgroups, users, customers, products, etc. just limited to their groups.

In Admin portal there is a new tab Groups to manage them. Administrators can create groups and subgroups and assign or remove existing users, customers and products. Each group also has an api-key and optional data and persona. The data can define data used in resource or task dependencies to personalize to employees in a region or having a certain skill set. The persona similarly prompts the AI that's group specific. Prompts are additive so if Support and Support NA both have prompts, they will be combined.

On Team or Customer page, create new allows a group association and requires it if the administrator is in a group. The same is true of creating products. Editing a user has a control that shows the group tree and allows changing membership. Both pages have a groups selector to filter users by group. There is also a No Groups selection which shows all users that are not in any group.

There are limits to Group Administrator. Removing a user from a group promotes them to have less filtering. A Group Administrator can move users within their domain but not remove from a group that would make them invisible to that Administrator, or give them full access. An Account Administrator needs to do that. Only Account Administrators can create or assign that role. No role escalation is allowed.

Intelligence page and userlog page has group selector to filter activity by group. Userlog captures all activity, and Tasks and GPT sessions are also associated with the user's groups.

If a user, customer, or product is deleted, the associated group associations are also deleted.

Group data should be passed to app to filter resources, used in gpt and tasks for dependencies

Groups are not exchanged between author and expert environments

Coming soon: Product owners