# Administration

The Administration section allows you to manage component types your organization has subscribed to, as well as users and groups. It lets the YaK administrator set the appropriate rights and privileges to users and assign roles.

## Component types

This is where the administrator uploads and saves the component types for which a subscription to dbi services has been purchased.

## User Access Management

An introduction of user access management in YaK is given in this chapter, which covers the ways in which users, groups, and roles collaborate to limit who has the ability to view and edit resources on the platform.

YaK’s access system relies on four key components :

* [**Roles:**](#roles) Fixed access levels that specify each group member's permissions.
* [**Users:**](#users) Personal accounts
* [**Groups:**](#groups) User-containing organisational entities that manage access to resources

Every user in YaK is assigned to a group, and every user is required to be a member of at least one group. This configuration guarantees scalable, safe access control by managing permissions at the group level.

### Roles

YaK comes with 4 roles : "**Administrator**", "**Owner**", "**User**" and "**Viewer**".\
Each of these roles confers specific privileges.\
Roles details and the privileges they grant are described in a dedicated section (see [appendix/roles](https://dbi-services.gitbook.io/yak-user-doc/yak-release-2.0/appendix/roles)).

### Users

Only administrators are allowed to create users in YaK.

The administrator creates the user's account and allocates the user to one or more groups, as every user must be a member of at least one group to have access to resources.

User attributes include:

* Username, First name, Last name, Email and Password

The email address defined must be unique as it will be used to log into the application.

### Groups

Users are organized in groups and given collective access to resources.

A user must belong to at least one group.
