> For the complete documentation index, see [llms.txt](https://survey.fmpx.docs.frox-it.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://survey.fmpx.docs.frox-it.de/zusatzliche-module/m-fx-arcgis-named-user.md).

# M-FX ArcGIS Named User

Über Ihren Named User erhalten Sie eine direkte Verbindung zur ArcGIS Cloud. Wenn in Ihrer FX Survey Lizenz ein ArcGIS Named User freigeschaltet ist, so öffnet sich nach dem Start von FX Survey das folgende Fenster.

<figure><img src="https://content.gitbook.com/content/avDnAykoA7C7prWiDq6h/blobs/zjh30KUVshTGi2mppCrz/image.png" alt=""><figcaption></figcaption></figure>

Alternativ kann das Anmeldefenster über das Menü Hilfe / Lizenzinformationen und dort über den Reiter \<ArcGIS Named User> geöffnet werden.

<figure><img src="https://content.gitbook.com/content/avDnAykoA7C7prWiDq6h/blobs/aCMmoTMafaM5jNxekRmQ/image.png" alt=""><figcaption></figcaption></figure>

## Vorteile des cloudbasierten Arbeitens

* Über die Cloud stehen Ihnen verschiedene Grundkarten zur Verfügung.&#x20;
* Ihre Projekte können jederzeit direkt mit anderen Beteiligten ausgetauscht werden.
* Vernetztes Arbeiten mit FX Smart und FX Reality.


---

# 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://survey.fmpx.docs.frox-it.de/zusatzliche-module/m-fx-arcgis-named-user.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.
