> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/9.3-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/administration.md).

# Administration

In PUC, the Administration perspective can be used by logged-on users assigned a role that has permissions to administer security can perform system configuration and maintenance tasks.

If you see **Administration** in the left drop-down menu on the **Home** page, you can click it to reveal menu items specific to administration of the Pentaho Server. If you do not have administration privileges, **Administration** does not appear within the console.

![Administration perspective in PUC](https://698418877-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgb0b8jIz4HuPLxqQR6C4%2Fuploads%2Fgit-blob-2402aca43e4393a9cc070a9f9516127feea47035%2FssBaservAdminPerspective.png?alt=media)

| Item | Control Name       | Function                                                                                                                                                                                                                                     |
| ---- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1    | **Administration** | In PUC, open the **Administration** perspective. The **Administration** perspective enables you to set up users, configure the mail server, change authentication settings on the Pentaho Server, and install software licenses for Pentaho. |
| 2    | **Users & Roles**  | Manage the Pentaho users or roles for the Pentaho Server. [Learn more](https://docs.pentaho.com/pba/9.3-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/administration/manage-users-and-roles-in-puc.md)              |
| 3    | **Authentication** | Set the security provider for the Pentaho Server to either the default Pentaho Security or LDAP/Active Directory. See the **Administer Pentaho Data Integration and Analytics** document for details.                                        |
| 4    | **Mail Server**    | Set up the outgoing email server and the account used to send reports through email.                                                                                                                                                         |
| 5    | **Licenses**       | Manage Pentaho software licenses. See the **Administer Pentaho Data Integration and Analytics** document for details.                                                                                                                        |
| 6    | **Settings**       | Manage settings for deleting older generated files, either manually or by creating a schedule for deletion.                                                                                                                                  |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pba/9.3-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/administration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
