> 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/administration/groups-and-permissions.md). # Groups and Permissions ## Roles, Groups & Method-Level Permissions Users can be organized into groups (e.g., admin group with full rights, read-only groups, groups with limited write access). Permissions are managed at the method level: individual methods can be made visible or invisible to specific users or user groups via the "Manage Methods" function. Example permission scenario: some users can view and add data but cannot delete objects. In the **Manage Methods** dialog the option **-All-** is active by default, which means no restriction applies. Choosing the option **-User groups-** instead releases the item explicitly for certain groups or individual users. The same mechanism covers methods, system databases, and queries. When user-rights restrictions are active in the user rights configuration, using and editing layouts and creating databases are not permitted by default. Both can be allowed for certain users. These restrictions apply to computer (Windows) user names only. External users may not have permission to modify shipped system data types - `System > System Configuration > Data Types` is effectively read-only for external users. Custom data type creation (`System > Data Types > New Data Type`) is available to users even when modifying existing system data types is restricted. --- # 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/administration/groups-and-permissions.md?ask=&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.