> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/platform-user-guide-book/administration/tenant/authorization.md).

# Authorization

<figure><img src="https://122097802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfEQ6KpTjmszWVWQqgcEa%2Fuploads%2FK6Z4Sl6HZJa4UoXerAkx%2FAuthorization%20page.png?alt=media&amp;token=a7b74700-0973-452c-93e4-b92177216ce9" alt=""><figcaption><p>Authorization</p></figcaption></figure>

1. **Enable  max attempts:** The Super Admin can set a maximum number of login attempts for all users. If a user exceeds this limit by entering an incorrect password multiple times, their account will be temporarily locked. To regain access, the user must contact an administrator to request a password reset via an email link.
2. **Enable IP address:** The Admin can restrict access to the Tenant by allowing only specific IP addresses. This ensures that only approved environments, such as company devices or users connected through a designated internal VPN, can access the platform, enhancing security and control.
3. **Login Type:** The Admin can choose between different authentication methods for user access:

   * **Normal Login:** Standard password-based authentication.
   * **Two-Factor Authentication (2FA):** Requires users to verify their identity using a third-party authenticator app (e.g., Google Authenticator or Microsoft Authenticator), which generates a unique code for secure access.
   * **Optional 2FA:** Users can decide whether to enable Two-Factor Authentication for added security.

   <figure><img src="https://122097802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfEQ6KpTjmszWVWQqgcEa%2Fuploads%2Fela75bjGOnX0JN7vuGGr%2Fimage.png?alt=media&amp;token=87bd5050-9295-4c43-aa5a-90c21b47aee8" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Download **Microsoft Authenticator** APP on your SmartPhone; \
**Android:** <https://play.google.com/store/apps/details?id=com.azure.authenticator&hl=en&pli=1>\
**Apple:** <https://apps.apple.com/us/app/microsoft-authenticator/id983156458>
{% endhint %}

{% hint style="success" %}
Download **Google Authenticator** APP on your SmartPhone; \
**Android:** <https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=en>

**Apple:** <https://apps.apple.com/us/app/google-authenticator/id388497605>
{% endhint %}


---

# 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.g-iot.io/platform-user-guide-book/administration/tenant/authorization.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.
