# Platform Usage

- [Configuration](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration.md)
- [License](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/license.md): The license is provided in the form of a token with a restricted time of validity.
- [LDAP](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/ldap.md): Datasentinel seamlessly integrates with LDAP for user authentication.
- [SMTP](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/smtp.md): SMTP (Simple Mail Transfer Protocol) is required for sending email notifications and workload reports. It ensures reliable delivery of messages, enabling real-time alerts and efficient report sharing
- [Audit](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/audit.md): Datasentinel can audit the actions performed by your declared users on the platform.
- [Default RBAC Behavior](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/default-rbac-behavior.md)
- [Users & Roles](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/users-and-roles.md): Datasentinel employs a multi-layered approach to secure user access to its platform and control who can access monitored PostgreSQL instances.
- [Backend](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/backend.md)
- [API Reference](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference.md)
- [Access Token](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/access-token.md): To enable interaction with the Platform API, it is necessary to generate an access token.This access token is subsequently used when making calls to the API.
- [Connection](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/connection.md): The Connection API is available solely through an on-premises installation and is reliant on the decision to use the Agentless feature.
- [Role](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/role.md)
- [User](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/user.md)
- [Reporting](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/reporting.md)
- [Workload](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/workload.md): The Workload API provides you with the option to download comprehensive metrics in either JSON or CSV format.
- [Alerting](https://docs.datasentinel.io/manual/implementation/platform-usage/api-reference/alerting.md)
- [Tooling](https://docs.datasentinel.io/manual/implementation/platform-usage/tooling.md): Datasentinel provides tooling to help you troubleshoot problems or gather information about system configurations.
- [Log Files](https://docs.datasentinel.io/manual/implementation/platform-usage/log-files.md): Datasentinel generates logs, which are located in the /datasentinel/log directory, except for the NGINX log file.


---

# 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://docs.datasentinel.io/manual/implementation/platform-usage.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.