> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/object-storage/details/users-and-permissions.md).

# Users and Permissions

A repository can have several S3 users, each with their own credentials and access level.

The concept is in [S3 access: users and credentials.](/docs-en/productos/object-storage/concepts/s3-access-users-and-credentials.md)

### User management

| Action             | What it does                                              |
| ------------------ | --------------------------------------------------------- |
| Create S3 user     | Registers an access identity with its credentials         |
| Enable or disable  | Enables or cuts off a user's access without deleting them |
| Rotate credentials | Renew the keys from **users › (…) › Keys**                |

### Permissions

Permissions are assigned granularly, over objects or sets of objects, so that each user or service accesses only what corresponds to them.

| Aspect | Detail                                                                                       |
| ------ | -------------------------------------------------------------------------------------------- |
| Scope  | Objects or sets of objects                                                                   |
| Why    | To give each user or service the right level of access, without opening the whole repository |

> #### 📘 One credential per service or per client
>
> Separating access by service or by client, with only the minimum necessary permissions, lets you revoke or rotate one without affecting the rest.
>
> It's the difference between cutting off a specific access and having to touch the whole repository.

### Where to continue

* The connection details and commands: [Credentials and S3 access.](/docs-en/productos/object-storage/details/credentials-and-s3-access.md)


---

# 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 dynamically by asking a question.

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

```
GET https://docs.plenit.com/docs-en/productos/object-storage/details/users-and-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.