> 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.4-user-interface/5.4.3-settings.md).

# 5.4.3. Settings

The GeoPrism Registry settings are accessible from the hamburger menu. The settings window is separated into different sections which are accessible depending on the user role:

<table><thead><tr><th>Section</th><th>Functionality</th><th data-type="checkbox">System Administrator</th><th data-type="checkbox">Registry Administrator</th><th data-type="checkbox">Registry Maintainer</th><th data-type="checkbox">Registry Contributor</th></tr></thead><tbody><tr><td>System information</td><td>Current version of GeoPrism Registry installed on the instance</td><td>true</td><td>true</td><td>true</td><td>true</td></tr><tr><td>System administrators</td><td>List and contact information of the user(s) having the System Administrator role</td><td>true</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Organizations</td><td>List of organizations registered in GeoPrism Registry and possibility to add new ones for the System Administrator role (see <a href="https://github.com/terraframe/geoprism-registry-documentation/blob/main/versions/current/3-deployment-and-setup/3.3-organization-management">section 3.3</a>)</td><td>true</td><td>true</td><td>false</td><td>false</td></tr><tr><td>User accounts</td><td>Management and invitation of users by the System Administrator and Registry Administrator roles and possibility for the Registry Maintainer and Registry Contributor to see the users of their own organization (see <a href="/pages/2hHYwrqnlVZsPFVSZbcI">section 6.3</a>)</td><td>true</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Localization</td><td>List of locales available in GeoPrism Registry and possibility to import and export new ones for the System Administrator role (see <a href="https://github.com/terraframe/geoprism-registry-documentation/blob/main/versions/current/3-deployment-and-setup/3.4-localisation">section 3.4</a>)</td><td>true</td><td>false</td><td>false</td><td>false</td></tr><tr><td>Branding</td><td>Functionality for the System Administrator role to change the logo on the upper left side of the GeoPrism Registry interface (see <a href="/pages/QxHXk2dldhGuYey8bz38">section 3.6</a>)</td><td>true</td><td>false</td><td>false</td><td>false</td></tr><tr><td>Email</td><td>Functionality for the System Administrator role to set the email address from and to which emails are being sent (see <a href="/pages/zucKeEByUNmzIQZ80dc2">section 3.5</a>)</td><td>true</td><td>false</td><td>false</td><td>false</td></tr><tr><td>External systems</td><td>List of external systems to which GeoPrism Registry is connected (see <a href="/pages/aR7PyubhSU7hnCFjh1PC">section 4</a>)</td><td>true</td><td>true</td><td>false</td><td>false</td></tr><tr><td>External system synchronizations</td><td>Functionality for the System Administrator and Registry Administrator to synchronize external systems with GeoPrism Registry content (see <a href="/pages/aR7PyubhSU7hnCFjh1PC">section 4</a>)</td><td>true</td><td>true</td><td>false</td><td>false</td></tr></tbody></table>


---

# 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.4-user-interface/5.4.3-settings.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.