> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/deployment-and-it-ops/identity-and-access/saml-sso-setup/okta-saml-sso.md).

# Okta SAML SSO

Configure SAML single sign-on with Okta, then send the metadata URL to We360 Support for activation.

Use this guide to configure Okta for We360 SAML SSO.

{% hint style="warning" %}
**We360 Support must activate SSO after your Okta setup.** Send Support the **Identity Provider Metadata URL** after step 4. SSO will not work until Support confirms activation. Do not test before that confirmation.
{% endhint %}

{% stepper %}
{% step %}

### Create a SAML application

1. Sign in to the Okta Admin Console at `https://<your-okta-domain>.okta.com/admin`.
2. Go to **Applications** → **Applications**.
3. Select **Create App Integration**.
4. Select **SAML 2.0**, then select **Next**.
5. Name the application, such as `We360 SAML`.
6. Select **Next**.
   {% endstep %}

{% step %}

### Configure SAML values

Enter these values exactly:

* **Single sign-on URL (ACS URL):** `https://auth.in.we360.ai/realms/ind-prod/broker/<domain>-okta/endpoint`
* **Audience URI (SP Entity ID):** `https://auth.in.we360.ai/realms/ind-prod`
* **Name ID format:** `EmailAddress`
* **Application username:** `Email`

Replace `<domain>` with your We360 portal subdomain.

For `https://mydomain.we360.ai`, use:

`https://auth.in.we360.ai/realms/ind-prod/broker/mydomain-okta/endpoint`
{% endstep %}

{% step %}

### Add attribute statements

Add these attributes:

* `email` — value: `user.email`
* `firstName` — value: `user.firstName`
* `lastName` — value: `user.lastName`

Set each attribute's name format to **Unspecified**. Select **Next**, then **Finish**.
{% endstep %}

{% step %}

### Send metadata to We360 Support

1. Open **Applications** → **We360 SAML** → **Sign On**.
2. Copy the **Identity Provider Metadata URL**.
3. Send that URL to We360 Support.

Support uses this URL to complete the We360-side SSO configuration. Wait for their confirmation before testing.
{% endstep %}

{% step %}

### Assign users or groups

Open **Applications** → **We360 SAML** → **Assignments**. Assign the users or groups that need SSO access.

{% hint style="danger" %}
Users cannot sign in unless they are assigned to the application.
{% endhint %}
{% endstep %}

{% step %}

### Test after activation

After Support confirms activation, open `https://<domain>.we360.ai` and start sign-in. You should be redirected to Okta.
{% endstep %}
{% endstepper %}


---

# 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.we360.ai/deployment-and-it-ops/identity-and-access/saml-sso-setup/okta-saml-sso.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.