> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/interface-authentication-and-access.md).

# Interface authentication and access

Interface security controls who can open and use a published interface. These settings are separate from permissions to edit the project in StackAI.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FqLyHCsytNRO3sr3qi1NT%2FG060.mp4?alt=media&token=4ed098b0-4849-4d06-977e-b06df71cc6ab>" %}

## Choose the access model

Open the project's **Interface → Security** settings. You need permission to edit and publish the interface. Choose based on who should be able to use it:

| Setting                                        | Audience and use                                                                                                                                                                                                                                                           |
| ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No password or sign-in requirement             | Public access through the interface link. Use only for an assistant intended for that audience.                                                                                                                                                                            |
| **Enable Password protection**                 | Visitors who know the shared password can use the assistant. It does not identify an individual user or select employees by membership.                                                                                                                                    |
| **Make it private to your organization (SSO)** | Requires organization access. Use for an internal assistant; add email/group restrictions when only part of the organization should use it.                                                                                                                                |
| **Require Authentication**, when available     | Login-only mode for Chat Assistant. This is distinct from organization SSO and is not an employee/group allowlist. It cannot be enabled at the same time as SSO.                                                                                                           |
| **Allowed source URLs**                        | Limits where an embedded interface may be accessed from. Enter the allowed source page URLs; this is not a list of user email domains. Use the exact referring page URL, including its path and relevant trailing slash, rather than assuming an entire domain is allowed. |

For an internal audience, enable **Make it private to your organization (SSO)**. If only selected people should have access, enable **Restrict access by email or group** and select the intended organization members or groups. Your email is added when the restriction is enabled; review the full selection. An empty selection removes that narrower restriction rather than denying everyone. If a person or group is missing, ask an administrator to review [membership](https://docs.stackai.com/guides-and-quickstarts/organization-administration/members-and-invitations.md) or [groups](https://docs.stackai.com/guides-and-quickstarts/organization-administration/groups-and-membership.md) before publishing.

Use [SSO setup](https://docs.stackai.com/guides-and-quickstarts/organization-administration/sso-setup.md) if your organization needs identity-provider configuration. Conversation-share links have separate behavior: read [Share a conversation](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/share-a-conversation.md) before sharing a transcript.

## Configure interface security

Set the access method selected above. To set a password, use the edit control, enter the value, and save it with the checkmark. To restrict SSO access, review the selected email addresses and groups before saving the interface.

![Published interface security settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/LMwYrzlkPgW0s7dFLmBs/assets/g060-g060-01-security.png)

Save password or sign-in settings before checking the published interface.

## Publish the settings

Publish the saved configuration and confirm publication completes.

![Interface security publication controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/vI6q6fgIwS9X9LRkyeej/assets/g060-g060-02-publish.png)

Unsaved or unpublished settings may differ from what end users currently see.

## Open the protected interface

Open the **Published Interface** in a separate browser profile or private window without an existing session. Then test again as an intended user. For an email/group restriction, also test an account outside that selection.

![Published interface authentication prompt](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/VnaAiQC1LlLHJrOebcYO/assets/g060-g060-03-gate.png)

Confirm that the required access check appears before the conversation controls. The intended user should be able to submit a request; the user outside the allowed audience should be denied. Test through the published link, not Draft Preview.

## Understand a rejected password

If a password is rejected, check the value you entered and try again.

![Rejected interface password message](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/EcjIxk8bYNQM9D9bsfsy/assets/g060-g060-04-rejection.png)

The conversation remains unavailable until authentication succeeds.

## Authenticate and use the assistant

For password protection, enter the correct password through the access prompt. For SSO or login-only mode, complete the sign-in flow using the intended account.

![Authenticated assistant conversation view](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/sR7uIVkTGHzxiwjPAafe/assets/g060-g060-05-unlocked.png)

Confirm that the assistant's welcome screen becomes available after successful authentication.

After authentication, enter a request.

![Authenticated assistant conversation view](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/osFvqXaIOXwTD4CqlXUN/assets/g060-g060-06-answer.png)

The assistant runs the connected workflow and displays its response.

## If access does not match your settings

Confirm that both Save and the required [publication process](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/publish-and-unpublish-a-project.md) completed. Check which account is signed in and which organization is selected. For SSO restrictions, review the selected emails and current group membership. If both SSO and **Require Authentication** are enabled, choose one supported mode and publish again. If an embedded interface reports an origin or source-URL error, compare **Allowed source URLs** with the referring page URL, including its path and trailing slash. Changing the password does not fix a source-URL mismatch.

## Important behavior

Save and publish security changes before checking the end-user interface. The draft can differ from the published configuration.

## Continue

* [Publish a Chat Assistant](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-chat-assistant.md)
* [Share a conversation](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/share-a-conversation.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://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/interface-authentication-and-access.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.
