> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/geodin-desktop/es/administracion/groups-and-permissions.md).

# Grupos y permisos

## Roles, Grupos y permisos a nivel de Método

Los usuarios pueden organizarse en Grupos (p. ej., grupo de administración con derechos completos, Grupos de solo lectura, Grupos con acceso de escritura limitado).

Los permisos se gestionan a nivel de método: los métodos individuales pueden hacerse visibles o invisibles para usuarios específicos o Grupos de usuarios mediante la función "Gestionar Métodos".

Escenario de permisos de ejemplo: algunos usuarios pueden Vista y añadir datos, pero no pueden Eliminar Objeto.

Los usuarios externos pueden no tener permiso para modificar los tipos de datos del sistema enviados - `Sistema > Configuración del sistema > Tipo de datos` es efectivamente de solo lectura para los usuarios externos.

Creación de Asignar tipo de datos Definido por el usuario (`Sistema > Tipo de datos > Nuevo tipo de datos`) está Disponible para los usuarios incluso cuando modificar los tipos de datos del sistema existentes está restringido.


---

# 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.geodin.com/geodin-desktop/es/administracion/groups-and-permissions.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.
