> For the complete documentation index, see [llms.txt](https://docs.geoprismregistry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geoprismregistry.com/readme/current-1/geoprism-registry-key-components/5.3-user-roles-and-their-rights/5.3-user-roles-and-their-rights-1.md).

# 5.3.2. Rights by role

Tables 5.1 and 5.2 outline the rights by role currently implemented in GeoPrism Registry. These are organized according to the steps in the common geo-registry data/information flow (Figure 5.7; see [Ebener (2022)](https://healthgeolab.net/DOCUMENTS/Guidance_Common_Geo-registry_Ve2.pdf)):

![Figure 5.7: Common geo-registry data/information flow.](https://lh5.googleusercontent.com/-CR9Ja-Sp0pcDLp4Pw10qV_02iquXyUJZqWK2nac8uKDrQ2jqZXHQC24oolVCvCqZVCdZ-aozpO4tn8lLpdeee_zyGM4t4PmjYRw_dPhEqXhd-2nGh-0rQxwKtXjrmAu0GcT5Yg9jWACJJIf-BLNyM2MmvF2UbtKnRKY3P9jCM9QdzcgwAVoTvUx8g)

The legend for the numbers listed next to each role in Tables 5.1 and 5.2 is as follows:

1. For all organizations
2. For their organization, for all Geo-Object Types
3. For their organization, for Geo-Object Types over which the user has a curation mandate

Two examples on how to the decipher the table for each role:

* Cell highlighted in gray (Table 5.1): the System Administrator role can view the information of all organizations.
* Cell highlighted in blue (Table 5.1): The Registry Administrator can manage data elements (including classification tables) for all the Geo-Object Types and/or hierarchies private to their organization

![Table 5.1](/files/hn96gPiusR3dovorf1vo)

![Table 5.2](/files/gWX7Ny5hXa57VU4Cdgtn)


---

# 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.geoprismregistry.com/readme/current-1/geoprism-registry-key-components/5.3-user-roles-and-their-rights/5.3-user-roles-and-their-rights-1.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.