# Security

{% hint style="info" %}
Data security is crucial for protecting sensitive and confidential information, and for maintaining the integrity and availability of data. PDQ security helps protect sensitive and confidential information from unauthorized access, use, disclosure, disruption, modification, or destruction. 

Data security can be achieved through a combination of physical, technical, and administrative controls. By selecting the Security under the settings tab, the user can view all the users across the organization and their permissions levels within the platform.
{% endhint %}

<figure><img src="/files/BgtigmEPduK9lcYIXJd7" alt=""><figcaption></figcaption></figure>

There are 3 feature options:

{% tabs %}
{% tab title="User" %}
{% hint style="info" %}
Manage users across the organization and their permission levels for the portal. It provides the details of Total users, Active Users, and Inactive Users.&#x20;

You can also invite Users from this section by providing the Email and Role details. The different default roles in PDQ are as follows:

● Admin: Admins are responsible for the overall administration of the platform&#x20;

● User - Users can read all discovered properties and metrics&#x20;

● Steward - Stewards are responsible for managing asset connections and discovered properties&#x20;

● QA User - Custom definition for your control and use
{% endhint %}

1. Invite a User and select a Role.

<figure><img src="/files/sQE0RnNRg6xI1cMFn9Yj" alt=""><figcaption><p>Invite a User</p></figcaption></figure>

{% hint style="info" %}
An admin user also possesses the following controls within the Security page:

1. Add/Modify the First Name of the user
2. Add/Modify the Last Name of the user
3. Add/Modify the Title of the user
4. Assign specific Domains to the user
5. Assign specific Applications to the user
6. Change the Roles of a user
7. Enable/Disable the access to a user using the Active section
8. Delete a User
9. Trigger a password reset link via email
10. Reset password for other users from the settings page
    {% endhint %}
    {% endtab %}

{% tab title="Roles" %}
{% hint style="info" %}
Under the Roles tab, an admin user can create new custom roles and modify their privileges as per their need.&#x20;

Under the features section, there are 3 different access options for various features within the platform:

● N - None&#x20;

● V - View only

● E - Edit
{% endhint %}

<figure><img src="/files/OunEzJME9dlW4Wz9d7XH" alt=""><figcaption><p>Roles - Admin</p></figcaption></figure>
{% endtab %}

{% tab title="Activity" %}
{% hint style="info" %}
As the name indicates, this section collects logs of the user activity and displays them for tracing back one's activities.&#x20;

Information such as:

User name&#x20;

Last login details&#x20;

No. of audit logs&#x20;

Duration statistics

Session start time

Session end time

IP address&#x20;

Audit information
{% endhint %}

1. Click on the Activity tab.

<figure><img src="/files/CJIEyHumTcWJpJgvyr00" alt=""><figcaption><p>User Activity</p></figcaption></figure>

{% hint style="info" %}
● The admin/privileged user can also push the user sessions and user activity tables to the metadata repository&#x20;

● The admin/privileged user will be able to view the following options on the user activity page under the settings > General> Reporting:&#x20;

&#x20;   ○ Run now&#x20;

&#x20;   ○ Schedule&#x20;

● The admin/privileged user will be able to delete/update the existing schedule and should be able to see the next run date time&#x20;

● The admin/privileged will be able to view the following metadata properties in the target table based on the setup in the Reporting settings
{% endhint %}

#### User Activity

<table><thead><tr><th width="224">Metadata</th><th>Description</th></tr></thead><tbody><tr><td>ATTRIBUTE_ID</td><td>The unique identifier of the attribute in PDQ. Used to join USER_METADATA.</td></tr><tr><td>ATTRIBUTE</td><td>The name of the attribute/column against which the user acts PDQ</td></tr><tr><td> AUDITTYPE</td><td>The type of action that the user performs against the asset, can be the update of metadata properties, adding a dataset, deleting a dataset, etc. There are currently 19 unique options being catalogued. </td></tr><tr><td>NOTIFICATION_TEXT</td><td>The alert/notification text that is generated in the PDQ platform for the user's actions.</td></tr><tr><td>CREATED_DATE</td><td>he timestamp at which the user performed the respective action. I believe this is UTC.</td></tr><tr><td>USERNAME</td><td>The name of the user in the PDQ platform</td></tr><tr><td> USER ROLE</td><td>The role of the user assigned in PDQ</td></tr><tr><td>ASSETS</td><td>Name of the data source/dataset/attribute in which the action has been performed by the user in PDQ.</td></tr><tr><td>CONNECTION_ID</td><td>The unique identifier of the data source. Use to join to USER_METADATA DATASOURCE_ID.</td></tr><tr><td>USER_ID</td><td>The unique identifier of the user in PDQ. unique to PDQ - does not correspond to Employee ID.</td></tr></tbody></table>

#### UserSessons

<table><thead><tr><th width="227">Metadata</th><th>Description</th></tr></thead><tbody><tr><td>MAX_SESSION_TIME</td><td>The highest duration a user has been logged into the platform.</td></tr><tr><td>MIN_SESSION_TIME</td><td>The lowest duration a user has been logged into the platform.</td></tr><tr><td>TOTAL_LOGIN_COUNT</td><td>The number of times a user has logged into the PDQ platform.</td></tr><tr><td>USER_ID</td><td>Auto Generate ID assigned to a user in PDQ.</td></tr><tr><td>USERNAME</td><td>Name of the user provided in PDQ.</td></tr><tr><td>USER ROLE</td><td>The role of the user is assigned in PDQ, and every role is assigned a set of permissions.</td></tr><tr><td>AUDITS_COUNT</td><td>Number of actions a user performed in PDQ.</td></tr><tr><td>AVG_SESSION_TIME</td><td>The average time spent on PDQ by a user.</td></tr><tr><td>LAST_LOGGED_IN</td><td>The recent login time of the user in PDQ</td></tr></tbody></table>

x

x

x

{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://academy.pentaho.com/data-quality-en/pentaho-data-quality/pdq-settings/security.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.