Selecting the right type of role
There are 5 key types of roles in K.
This page is to help K Administrators and K champions consider how they want to set up K user roles for their organisations.
5 K Roles
The users of K
Refer to the Role Permissions page for a detailed table of what each role has access to.
Role Hierarchy
Roles and their permissions are inherited (except where you specifically customise them to not to).
Data users inherit the same capabilities as Business users except Business user search and experience is geared towards Content (reports etc) whilst Data users prioritise Data (Tables, code etc)
Data Governance inherit the same capabilities as Data Users with elevated privileges to manage collections, ownership, stewardship configuration. They also have access to governance insights.
Data Managers inherit the same capabilities as Data Governance with the ability to see ecosystem level insights.
Roles higher up the hierarchy override roles that are below.
This means there is no need to add a Data Manager as a Data User as well. A Data user that is also added as a Business user will have the same restricted applied to a Business user.
Role restrictions defined by you will not be inherited. For example if you disable editing collections for a data manager roles, it will not restrict data governance roles by default and vice versa.
Aligning K roles to your organisation
Whilst every organisation is different, the following principles should be followed
Role | Organisation | Notes |
|---|---|---|
Business user | Anyone that is not a data worker (data analyst, scientist, engineer etc) | Can be setup to default to this role on login without having to be added to a group/role |
Data user | A data worker (data analyst, scientist, engineer etc) | |
Data Governance | A person responsible for managing and governing the use, classification, description and access to data | |
Data Manager | Person(s) responsible for the oversight of the data platforms in your organisation |