# Advanced

Limit Risotto to people from some email domains, and give Risotto's agents extra instructions about your organization

These settings should be modified with guidance from the Risotto team. Go to **Settings > Advanced**. Org Admins and Managers see this page.

> **Warning:** Consult the Risotto team before you change these settings. A wrong value can
> change how Risotto processes requests and how it talks to people.

The **Advanced Settings** card has two fields: **Domain filter regex** and **Additional instructions**.

*Product example: The Advanced settings page in the Risotto dashboard, with an empty domain filter and three additional instructions.*

## Change a setting

1. **Open the advanced settings**

   Go to **Settings > Advanced**.

2. **Enter the value**

   Type a regular expression in **Domain filter regex**, or type text in
   **Additional instructions**.

3. **Save**

   Click **Save** in the top-right corner of the card. The message "Settings
   saved" appears. To discard your changes instead, click **Cancel**.

   *Product example: The Advanced Settings card in the Risotto dashboard with the domain filter ^northwind\\.com$ typed, and Save.*

If the domain filter is not a valid regular expression, Risotto does not save it, and the message "Failed to save settings" appears.

## Advanced settings

### Domain filter regex

Only process messages from users whose email domains match the following [regex](https://regex101.com/).

Risotto compares the regular expression with the part of the sender's email address after the `@`. The filter applies to:

- Messages in Slack
- New Jira issues and Jira comments, by the email address of the reporter or the comment's author

When the domain does not match, Risotto ignores the message. When Risotto cannot find the sender's email address, it processes the message.

The regular expression can match any part of the domain. For example, `northwind\.com` also matches `northwind.com.au` and `mail.northwind.com`. To match one domain exactly, start the expression with `^` and end it with `$`:

- `^northwind\.com$`: only people with a @northwind.com email address
- `\.northwind\.com$`: people from any subdomain of northwind.com, such as @eu.northwind.com
- `^northwind\.com$|\.contoso\.org$`: people from northwind.com or from any subdomain of contoso.org

Leave the field empty to process messages from all users regardless of their email domain.

**Common use cases:**

#### Use case 1

Company has multiple domains

A company may have acquired another at some point or manages multiple brands. Employees are in a single Slack org, but have different Okta, Google workspace, and knowledge bases.

Multiple Risotto orgs can be deployed to the same Slack org. When an employee of company A has a request, Risotto org A responds. When an employee of company B makes a request, Risotto org B responds.

This can happen in one channel, so all employees can share a single #ask-it channel and each Risotto org responds to its own employees.

#### Use case 2

Company separates contractors by domain

Some companies give contractors a subdomain of their main email domain, such as `c.northwind.com`. A Risotto org can be configured to not respond to contractors.

A second Risotto org could then be deployed to respond only to full-time employees, whose email addresses do not have the `c.` subdomain.

#### Use case 3

Multi-tenant deployments

In shared Slack workspaces, different Risotto instances can be configured to respond only to their respective user populations by filtering on email domains. This ensures each organization's Risotto only handles requests from their own employees.

### Additional instructions

Additional context that Risotto can use to help your team.

> **Warning:** Less is more with additional instructions. Adding too much can have negative
> impacts.

> **Tip:** LLMs respond better to statements that say what to do than to statements that
> say what not to do.

Risotto adds this text to its AI prompts as instructions from your company. The support agent and automations use it. If an instruction conflicts with Risotto's own system prompt, Risotto ignores the instruction.

Use the field for:

- **Company-specific terminology**: Define internal terms, acronyms, or product names
- **Process guidelines**: Specify how Risotto should handle certain types of requests
- **Cultural context**: Provide information about team preferences or communication style
- **Technical environment**: Describe your organization's technology stack or constraints

**Examples:**

- "Our company uses 'Widgets' to refer to our main product line"
- "Always suggest contacting the Platform team for Kubernetes-related issues"
- "Prefer solutions using our internal tooling when available"

Keep instructions concise and focused on information that would genuinely help improve response quality. Overly detailed or contradictory instructions may reduce effectiveness.

Source: https://www.tryrisotto.com/docs/dashboard/settings/advanced
