> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/ja/user-guide/administration/system-configuration/collector-management/mobile.md).

# モバイル

このタブでは、Intune およびクライアントモバイルデバイスで Nexthink Mobile を設定するためのインストールトークンを作成できます。

新しいトークンを生成するには、**インストールトークンを生成** を選択し、次の値を入力します：

* **名前**: トークンに一意でわかりやすい名前を付けます。
* **有効期限**: トークンの有効期限を設定します。最大有効期間は 1 年で、これがデフォルト値でもあります。

<figure><img src="https://3549141153-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeLm8O7QKZDn6z806e7Sv%2Fuploads%2Fgit-blob-96c0d69bb25f9ad0926b64db4d5b273b15139494%2Finstallation-token-tab-collector.png?alt=media" alt="Generating an installation token"><figcaption></figcaption></figure>

既存のトークンを管理するには、そのトークンにカーソルを合わせて、右側のアクションメニューにアクセスします：

* **編集**: トークンの名前を変更します。既存のトークンの有効期限は変更できません。
* **トークンをコピー**: トークンをクリップボードにコピーします。
* **削除**: トークンを完全に削除します。この操作は元に戻せません。

<figure><img src="https://3549141153-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeLm8O7QKZDn6z806e7Sv%2Fuploads%2Fgit-blob-45a21163e329b121da35dd46339a8b5646bf42c6%2Finstallation-token-copy.png?alt=media" alt="Managing existing tokens"><figcaption></figcaption></figure>


---

# 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.nexthink.com/platform/ja/user-guide/administration/system-configuration/collector-management/mobile.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.
