> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Portal

> The Portal is a branded, self-service home where end users and guests open requests, chat with an AI agent, track tickets, and act on approvals and tasks.

The Portal is the self-service home for people who need help but do not work tickets themselves. End users and <Tooltip headline="Organization guests" tip="Users with limited, workspace-scoped access" cta="Learn about guests" href="/documentation/platform/roles-access">organization guests</Tooltip> use it to open requests, chat with an AI agent, track their tickets, and act on approvals and tasks, all from a branded page you control.

<Callout icon="link" color="#6B7280">
  Admins and workspace members who work tickets use [Admin](/documentation/platform/admin) instead.
</Callout>

## Mental model

The Portal is the self-service surface for users who are not workspace members. It shares one sign-in with Admin; a user's role decides which surface they land on.

* **Organization admins and workspace members** open the Admin.
* **Organization guests and non-members** open the Portal.

The Portal has two entry points:

* **Organization home** (`/home`): lists Portal-enabled workspaces plus an optional organization-level chat.
* **Workspace home** (`/{workspace}/home`): the branded home for a single team, with chat and the Start new request, Favorites, My requests, My approvals, and Tasks tabs.

Tickets created through the Portal are recorded with a **Portal** source.

***

## What gates visibility

Three independent settings control what a requester sees:

| Setting               | Level        | Controls                                                                                                    |
| --------------------- | ------------ | ----------------------------------------------------------------------------------------------------------- |
| **Guest visibility**  | Organization | Whether guests can access the organization and its Portal at all. Off by default.                           |
| **Portal**            | Workspace    | Whether a workspace appears in the portal and its agent can answer portal chat.                             |
| **Feature in Portal** | Form         | Whether a form appears on the **Start new request** tab. Non-featured forms still show in the full catalog. |

Form <Tooltip headline="Audience" tip="Everyone, Members only, or specific user groups" cta="Learn about audience" href="/documentation/tickets/forms/overview">audience</Tooltip> settings apply on top of this. Only published forms whose audience includes the requester appear, and private folders are hidden.

***

## Chat and ticket creation

Portal chat is powered by a connected published agent. The agent answers from knowledge, and when a request needs a ticket, it creates one and routes it to the appropriate workspace. Without a connected agent, requesters rely on forms.

When a Portal conversation is routed to an agent, that agent is shown as the **Working on it** owner on the resulting ticket until it is published to a human channel.

<Callout icon="link" color="#6B7280">
  Learn how the **Working on it** owner behaves in [Roles](/documentation/tickets/roles#working-on-it-agent-owner).
</Callout>

***

## Notifications

Portal-only requesters are notified by email: on ticket creation, on new messages, and when added as an approver. There is no in-portal notification inbox.

***

## Constraints and gotchas

* Guest visibility is off by default. Guests cannot reach the Portal until an admin enables it.
* A workspace only appears in the portal when its **Portal** setting is on.
* The **Start new request** tab shows only featured forms. Other accessible published forms appear in the full catalog.
* Portal chat requires a connected published agent. Without one, only forms are available.
* Requesters cannot edit ticket properties such as status, priority, or assignee. They create requests and add public messages.
* The Portal has no notification inbox. Updates reach requesters by email.