> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/settings/initial-setup.md).

# Initial Setup

### Default Login:

{% hint style="info" %}

* This step is required if the instance is being configuring for the first time.
* A tenant onboarded by a platform administrator uses the one-time **`LOGIN CODE`** shown when the tenant was created instead. See [Onboard Tenant](/product-guides/integral-zone/iz-suite/iz-core/multi-tenancy/onboard-tenant.md)
  {% endhint %}

1. Navigate to the UI and click on **`Signin with IZ User`**
2. Enter the credentials provided by Support Team and click on **`Login`** 

### Enable Anypoint SSO:

#### In Anypoint Platform

1. Login to <https://anypoint.mulesoft.com/>
2. Navigate to **`Access Management`** -> **`Connected Apps`**
3. Click on **`Create App`** and select the following details
   1. Name - IZ Suite Web
   2. Type - App acts on behalf of a user
   3. Grant types - Authorization Code
   4. Website URL - URL that will be displayed to the users
   5. Redirect URIs - \<FALCON\_HOST>/anypoint\_auth
   6. Add Following Scopes -
      1. Open ID -> Profile
4. Click on Save
5. Note the **`Client Id`** and **`Client Secret`** which will be used in the next step

#### In IZ Suite

1. Navigate to **`Global Settings`** -> **`Settings`**
2. Search for Auth and edit the **`Anypoint Auth`** settings&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F80Qpzm0WvbZoas6okE0f%2Fenable-anypoint-auth.png?alt=media&amp;token=436af28d-8216-4003-a2d8-9a3fa2ae791c" alt=""><figcaption></figcaption></figure>

3. Update the value of **`Is Enabled`** key to **`true`**
4. Update the value of **`Client Id`** key to the Connected Apps Client Id
5. Update the value of **`Client Secret`** key to the Connected Apps Client Secret
6. Click on **`Save`**
7. Logout and Login using **`Signin with CloudHub`**
8. Enter the License key shared by the Integral Zone support team

### Disable IZ User Login:

1. Navigate to **`Global Settings`** -> **`Settings`**
2. Search for Auth and edit the **`IZ User Auth`** settings&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FgX7wQevBbslL6uMPUbOg%2Fdisable-iz-token.png?alt=media&amp;token=45b8da57-dfcf-4fa6-976c-6fdc8a8fba63" alt=""><figcaption></figcaption></figure>

3. Update the value of **`Is Enabled`** key to **`false`** and click on **`Save`**

### See Also

* [Create Agent](/product-guides/integral-zone/iz-suite/iz-core/agent/create-agent.md)
* [Update Agent](/product-guides/integral-zone/iz-suite/iz-core/agent/update-agent.md)


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/settings/initial-setup.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.