<commit_before># DEFINITIONS

This guide will help you to understand the basic DBaaS architecture.

Basically DBaaS has 2 kind of users (if you run the `reset_data` command):

* Regular user: Can manage projects, databases and credentials.
* DBA user: Regular user roles +  physical and logical structure.


## 1. Account APP

![](./img/account_app.png "Account APP View")

### 1.1 Roles
You can create one or more roles you want assign appropriate permissions. We are using 2 kinds of roles: regular and DBA user.


### 1.2 Teams
It's sort of proxy for roles. The team has only one role, but one or more users. Subsequently those users inherit the team rule


### 1.3 Users
Users in the system. The user must have a team for usage.
<commit_msg>Update DEFINITIONS.md<commit_after># DEFINITIONS

This guide will help you to understand the basic DBaaS architecture.

Basically DBaaS has 2 kind of users (if you run the `reset_data` command):

* Regular user: Can manage projects, databases and credentials.
* DBA user: Regular user roles +  physical and logical structure.


## 1. Account APP

![](./img/account_app.png "Account APP View")

### 1.1 Roles
You can create one or more roles you want assign appropriate permissions. We are using 2 kinds of roles: regular and DBA user.


### 1.2 Teams
It's sort of a proxy for roles. The team has only one role, but one or more users. Subsequently those users inherit the team role.


### 1.3 Users
Users in the system. The user must have a team for usage.

{'fraction_non_alphanumeric': 0.07195203197868089, 'fraction_numerical': 0.011992005329780146, 'mean_word_length': 3.8925081433224755, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7013458', 'n_tokens_mistral': 445, 'n_tokens_neox': 408, 'n_words': 232}