# Departments

Create departments and set each one's ticket prefix, agent channel, members, escalations, auto-resolve, ticket sync, and additional ticket fields

A department is a team that handles one kind of request, such as IT, People, or Finance. Each department has its own tickets, members, and settings. Risotto uses each department's description to route a request to it. A request that matches no department goes to the default department.

To watch a department set up and a request from Slack routed to it, see the [two-minute video](https://www.tryrisotto.com/docs/guides/departments-video).

## Department management

### Department list

The **Departments** group in the Settings sidebar lists the departments you can edit. Each sub-department is listed under its parent. The default department has a **Default** badge.

To see all of them in a table, click **Departments** in the breadcrumb at the top of any department's settings page. The **Departments** page lists each department with its **Ticket prefix** and **Members** count.

*Product example: The Departments page in Risotto's settings, listing each department with its ticket prefix and member count, and New department.*

A department can have sub-departments, such as **IT / Networking**, that share its knowledge, tools, and agent channel but keep their own tickets, members, and escalation rules. See [Sub-departments](https://www.tryrisotto.com/docs/dashboard/settings/sub-departments).

### Create a department

Only Org Admins and Managers can create departments.

1. **Open the Create Department dialog**

   Click **+** next to **Departments** in the Settings sidebar. You can also click **New department** on the **Departments** page.

2. **Choose a parent**

   Leave **Parent department** at **None (top-level)**. To create a sub-department, pick its parent instead.

3. **Name and describe the department**

   Enter a **Name** and a **Description**. Both are required. Describe the requests the department handles: Risotto uses the description to route requests.

4. **Create the department**

   Click **Create**. Risotto picks a ticket prefix from the name and opens the department's **General** page, where you can change the prefix and set the agent channel.

   *Product example: The Create Department dialog over the Departments page, filled in for a Security department, and Create.*

A new department starts with the settings of the default department.

### A department's settings page

Click a department in the Settings sidebar, or on the **Departments** page, to open its settings page. The page lists the settings pages of the department in groups:

- **General**, **Members**, and **Assistant**. **Assistant** shows only to Org Admins and Managers.
- **Tickets**: **Priority**, **Ticket Sync**, and **Additional Ticket Fields**.
- **Workflow**: **Escalations**, **SLAs**, and **Auto Resolve**.
- **Sub-departments** (top-level departments only), with **New sub-department**.
- **Danger zone**: **Make Default…** and **Delete Department…**.

*Product example: The IT department's settings page, listing its settings pages by group, its Networking sub-department, and the Danger zone.*

Click a row to open that page. To rename the department, click its name at the top of any of its settings pages.

The **Priority** page holds the urgency criteria and the **VIPs** list for the department. See [Ticket Priority](https://www.tryrisotto.com/docs/dashboard/settings/ticket-priority).

The **SLAs** page holds the response and resolution targets for each priority. It shows only when ticket SLAs are on for your organization. See [Ticket SLAs](https://www.tryrisotto.com/docs/dashboard/settings/slas).

The **Assistant** page has the department's **Start automatically when a ticket escalates** setting. See [Assistant](https://www.tryrisotto.com/docs/dashboard/assistant#getting-started).

## General settings

Open **Settings > \<department> > General**. The **General Settings** card holds the settings below. After you change one, click **Save**, or click **Cancel** to discard your changes.

*Product example: The General page of the IT department's settings, with its description, ticket prefix, agent channel, review switches, and Save.*

### Description

A detailed description helps Risotto route requests correctly. Describe the kinds of requests the department handles. The description is required.

### Ticket prefix

Tickets created for this department are prefixed with this value. For example, with the prefix **IT**, a ticket is numbered **IT-41**.

- The prefix is 2 to 10 letters.
- Each department needs its own prefix.
- A sub-department's prefix comes after its parent's, which the page shows locked in front of the field. For example, **NET** under **IT** gives tickets such as **IT-NET-7**.

If an older department has no prefix, the field shows "This department has no ticket prefix. Enter one and save."

The number after the prefix comes from one counter for the whole organization, so the departments share one sequence, for example IT-101, HR-102, IT-103. Numbers start at 1, go up by one for each new ticket, and are not padded with zeros. You cannot set the start number. When you move a ticket to another department, it gets the new prefix and keeps its number.

### Agent channel

The **Agent Channel** is the Slack channel where agents can provide support. When a DM is classified under this department, Risotto posts a message in this channel for agent support. Pick the channel in the channel picker.

This creates a dedicated space for your team to collaborate on support requests and see when Risotto needs help.

A [sub-department](https://www.tryrisotto.com/docs/dashboard/settings/sub-departments) uses its parent's agent channel. Its **General** page shows the parent's channel name as inherited, and you cannot set a different one there.

When a department has no agent channel and the request is in a Slack channel, Risotto tags the escalation contact in the requestor's own thread. The requestor sees the tag, so Risotto does not also send the default "We're on it!" message there. When the department has an agent channel, the requestor still gets that message. A custom escalation message is always sent.

#### Ticket list in agent channel

Below the agent channel, the **Ticket list in agent channel** switch (marked **Experimental**) mirrors the department's tickets into a sortable list in its Slack agent channel. It needs an agent channel to be set. The switch is on the top-level department's page only, because a sub-department uses its parent's channel. An Org Admin, a Manager, or a Supervisor of the department can turn it on or off.

- The list is a Slack List named **Risotto Tickets (#channel)**. All the departments that use the same agent channel share one list.
- The columns are **Ticket** (a link to the ticket in the dashboard), **Subject**, **Department**, **Status**, **Priority**, **Requestor**, **Assignee**, **Category**, and **Created**. You sort and filter the list in Slack.
- The list shows the tickets that have a thread in the agent channel and are not **Resolved**, **Closed**, or **Duplicate**. A row updates when the ticket changes and goes away when the ticket is finished. When you turn on the switch, Risotto adds the channel's active tickets.
- Members of the channel can read the list but cannot edit it.
- When you turn off the switch, the channel loses access to the list and the list stops updating.

Slack Lists need a paid Slack plan. On a free plan, the dashboard shows "Slack ticket lists require a paid Slack plan." The Risotto Slack app also needs the `lists:read`, `lists:write`, `bookmarks:read`, and `bookmarks:write` scopes. If your custom Slack app is older than these scopes, update it as described in [Update Slack App](https://www.tryrisotto.com/docs/guides/update-slack-app). Until the app has the scopes, turning on the switch fails and names the missing scope:

- With a custom Slack app: "Your Slack app doesn't have the `lists:write` permission that ticket lists need. Update its manifest in Settings > Integrations > Slack and reinstall it in Slack, then try again."
- With the Risotto Marketplace app: "The Risotto Slack app doesn't have the `lists:write` permission that ticket lists need. Contact Risotto support to enable ticket lists."

### Assign the ticket to the agent who comments

When this switch is on, an Agent or Supervisor of the department who comments on a ticket becomes its assignee, unless a person other than Risotto already holds the ticket. The switch shows this text: "An agent of this department who comments on a ticket is assigned it, unless someone other than Risotto already holds it."

- The switch is on by default. It saves when you click it.
- It applies to comments from Slack, the dashboard, the API, and connected ticketing systems such as Jira. Internal notes count.
- A comment from the requestor, or a comment on a resolved or closed ticket, does not assign the ticket.
- A new sub-department copies the setting from its parent.

See [When Risotto steps back](https://www.tryrisotto.com/docs/concepts/ticket-lifecycle#when-risotto-steps-back) for how a reply changes the ticket.

### Answer review

#### Require human review for knowledge answers

Escalate knowledge-based answers to the agent channel for review before sending them to users. Requires the agent channel to be set.

When enabled, Risotto checks with human agents before sharing knowledge base answers.

#### Require human review for runbook answers

Escalate runbook answers to the agent channel for review before sending them to users. Requires the agent channel to be set.

This applies whenever the agent follows a runbook on a ticket, whether the answer came from indexed knowledge or from a tool the runbook calls.

> **Note:** These two toggles are the only review controls, and both are per department.
> There is no organization-wide switch that holds every outgoing reply. Tool
> actions are governed separately: set **Requires approval** on the tool, or
> create an [approval policy](https://www.tryrisotto.com/docs/dashboard/settings/approval-policies), and
> the agent asks before acting instead of before replying.

### AI beta opt-in

The **AI beta opt-in** switch (marked **Experimental**) opts the department in to new agent capabilities and smarter models before they roll out to everyone. The agent may be less stable or predictable in the department while it is on.

## Escalations

Open **Settings > \<department> > Escalations** to set who Risotto tags or assigns when it escalates a request. After you change a setting, click **Save**.

### Escalation contact

Risotto tags this user or group when it needs help. This can be overridden per channel and department.

Click **Add escalation contact** and pick a team member who should be notified when Risotto needs human assistance with requests for this department.

### Custom escalation message

Turn on **Custom escalation message** to replace the default message that requestors get when their ticket is escalated to a human. The message can be up to 500 characters. When the department has **Share ticket URL with requestor** on (see [Ticket sync](#ticket-sync)), put `{ticket_url}` in the message to include the link to the ticket.

### Escalation routing

Route escalations to an assignee based on ticket attributes, the requestor's profile, and team availability. Rules run top to bottom — the first enabled match wins, and each rule can be switched on or off on its own.

Each rule can have ticket conditions and requestor profile conditions. Ticket conditions match on the ticket's **Category**, **Tag**, **Source** (Slack, Microsoft Teams, email, API, etc.), **Primary tool**, and **Priority**; requestor conditions match on fields from the requestor's profile. A rule with no conditions matches every ticket. When a rule matches, it assigns the ticket to a specific user or a group, or hands it off to a sub-department.

1. **Add a rule**

   Click **Add rule**. A rule named **New rule** opens at the bottom of the list, switched on.

   *Product example: The Escalations page of the IT department's settings, with its escalation contact, three routing rules, and Add rule.*

2. **Name the rule**

   Type a name in the rule's name field.

3. **Add ticket conditions**

   Click **Add ticket condition**, then pick the field, the operator (**Equals**, **Doesn't equal**, **Contains**, **Doesn't contain**, **Starts with**, or **Ends with**), and the value. With more than one condition, set **Match** to **any of** or **all of**.

4. **Add requestor conditions**

   To match on the requestor's profile, click **Add requestor profile conditions** and add the conditions.

5. **Choose who gets the ticket**

   Pick **Assign to a specific user**, **Assign to a group**, or **Hand off to a sub-department**, then pick the person, the people, or the sub-department. **Hand off to a sub-department** shows only when the department has sub-departments.

6. **Order the rules**

   Drag a rule by its handle to move it up or down. Use the switch on a rule to turn it off without deleting it.

7. **Save**

   Click **Save**. If a rule that is on has nobody to route to, the rule shows "Add routing — this rule matches tickets but doesn't have routing." and the settings are not saved.

A rule shows a warning when it can never run, for example "This rule matches every ticket — rules below it will never run." or "These conditions contradict each other, so this rule can never match." Collapsed, each rule shows a summary, such as "If priority is urgent → online round-robin across 3 people".

A group target picks one person from the people on the rule, in one of three modes:

- **Round robin** rotates through the people on the rule in order. It skips only the requestor.
- **Round robin (online in Slack)** rotates only through the people whose Slack status is active at the moment of the escalation. It also skips the requestor. The mode shows only when your organization uses Slack. See [Online round robin](#online-round-robin).
- **Fewest tickets assigned** picks the person with the fewest tickets that are not finished (Open, In progress, Awaiting response, Awaiting support, Awaiting approval, or Paused).

Only **Round robin (online in Slack)** looks at presence. The other two modes do not check working hours, out-of-office status, or dashboard or Slack activity, so a person on leave stays in their rotation until you remove them from the rule or switch the rule off. Each rule has its own on/off switch, so a rule for one shift can be turned on and off by hand.

#### Online round robin

**Round robin (online in Slack)** asks Slack for each person's presence when a ticket escalates. The collapsed rule reads, for example, "online round-robin across 3 people".

- **Who counts as online.** A person whose Slack presence is active. Slack marks a person away after about 10 idle minutes. Risotto keeps each answer for one minute. A person with more than one Slack account counts as online if any of them is active.
- **The rotation.** The turn passes only among the people who are online. A person who is away does not keep a place in the queue, and joins the rotation again at their place in the list when they come back.
- **Nobody online.** The rule assigns nobody, and Risotto tries the next rule, then the default, then the escalation contact.
- **People Risotto cannot check.** A person with no Slack account that Risotto knows about is skipped. If Risotto cannot read presence at all, for example because the Slack token was revoked, the rule rotates through everybody, like **Round robin**.
- **Microsoft Teams.** The mode is for Slack only. It does not show for an organization that uses Microsoft Teams.

> **Note:** Category conditions also match the AI's **suggested category**, so a category
> rule can route an escalation before anyone has manually confirmed the ticket's
> category.

If no rule matches, the default under "If nothing matches, the default below applies." is used. Set it to **Tag the escalation contact only** (notify without assigning) or to **Assign to**, then pick a specific user, a group, or a sub-department.

> **Note:** Escalation routing is separate from the runbook tools that assign a ticket.
> The [Update Ticket](https://www.tryrisotto.com/docs/dashboard/tools#update-ticket) tool assigns the
> ticket to the person that the runbook names, and it does not check department
> membership. The older **Assign Ticket** tool is deprecated: you cannot add a
> new one, but existing ones continue to work. An existing Assign Ticket tool
> assigns the ticket to the **Assignee Email** set in its configuration, or to a
> person the agent picks from **Allowed Assignee Emails**.

## Auto Resolve

Open **Settings > \<department> > Auto Resolve**. Each department can override how inactive tickets are handled:

- **Auto-resolve delay** - Business days of inactivity before a ticket is auto-resolved. Overrides the organization default; minimum 1 day, 0 disables it. A value here, including 0, wins over the organization setting for this department's tickets. Clear the field to use the organization default again; the empty field shows that default as grey placeholder text. Tickets in **Awaiting approval** or **Awaiting support** are never auto-resolved. See [Auto-resolve Delay](https://www.tryrisotto.com/docs/dashboard/settings/notifications#auto-resolve-delay) for the nudge that precedes resolution.
- **Skip auto-resolve for agent-assigned tickets** - When enabled, tickets assigned to a human agent are never auto-resolved for inactivity.
- **Escalate tickets waiting on customer** - Escalate tickets that have stayed in the **Awaiting response** status longer than this many wall-clock hours since the last chat reply. Leave blank or set to 0 to disable.

When the delay differs from the organization default, the page says so, for example "Tickets in this department will be auto-resolved after 3 days instead of 7." Click **Save** to apply your changes.

> **Note:** Risotto sends one reminder to the requestor before auto-resolving a ticket
> (see [Auto-resolve
> Delay](https://www.tryrisotto.com/docs/dashboard/settings/notifications#auto-resolve-delay)). There is
> no separate setting that re-prompts a requestor who has not replied to the
> agent's first suggestion; to nudge sooner, add a follow-up step to the runbook
> that handles the request.

## Ticket sync

Open **Settings > \<department> > Ticket Sync** to sync this department's tickets with an external ticketing system.

1. **Add a ticket sync**

   Click **Add ticket sync**. The button shows while the department has no ticket sync.

2. **Pick the system**

   In the **Add Ticket Sync for \<department>** dialog, pick **Jira**, **Linear**, **Freshservice**, **GitHub Issues**, **Datadog**, **Asana**, **Zendesk**, **Airtable**, or **ServiceNow**, and fill in its settings. These settings override the organization defaults.

Once the department has a ticket sync, the page shows these switches above the integration's card:

- **External ticket sync enabled**: create tickets in the connected ticketing integrations for requests in this department.
- **Only sync escalated tickets**: sync only the tickets that are escalated.
- **Share ticket URL with requestor**: share the ticket's URL with the requestor when their request is escalated.
- **Show external ticket ID**: show the external ticket ID (for example, JIRA-123) in the request channel.

To change an integration's settings later, open the **Connected** menu on its card and click **Configure...**.

## Additional ticket fields

Open **Settings > \<department> > Additional Ticket Fields** to add fields that capture information specific to this department's tickets — for example, a "Location" dropdown or an "Asset Tag" text field. Additional fields are scoped to a single department and only appear on tickets routed there.

### Creating fields

1. **Add a field**

   Click **Add your first field**, or **Add field** when the department already
   has fields.

2. **Name it and pick its type**

   Type the field's label, then pick its type from the table below. The type is
   fixed once the field is saved.

3. **Add the choices**

   For a dropdown, click **Add choice** for each choice and type its label. A
   dropdown needs at least one choice, and no two choices can have the same
   label.

4. **Add help text**

   Optionally, type help text to show under the field.

| Field type              | What it collects             |
| ----------------------- | ---------------------------- |
| Dropdown (single)       | One choice from a list       |
| Dropdown (multi-select) | Multiple choices from a list |
| Short text              | A single line of text        |
| Long text               | A paragraph of text          |
| Number                  | A numeric value              |
| Date                    | A calendar date              |
| Checkbox                | Yes/No                       |

Risotto derives each choice's stored value from its label. The value sent to Jira or ServiceNow is set separately (see [Syncing field values to Jira or ServiceNow](#syncing-field-values-to-jira-or-servicenow)).

> **Warning:** A field's type can't be changed after creation. Its label, choices, help text,
> and **Active** switch all stay editable.

### Setting field values on tickets

Once created, a field appears under **Additional fields** in the [ticket aside](https://www.tryrisotto.com/docs/dashboard/tickets/ticket-details#ticket-aside), where agents can set or clear its value directly.

A field gets a value only when something sets it. The agent does not fill in additional fields on its own. These are the ways to set a value:

- An agent sets it in the ticket's side panel.
- The [Assistant](#managing-fields-with-the-assistant) sets it when it creates or updates a ticket for you.
- The Risotto API sets it when it creates or updates a ticket.
- An automation sets it with the **Create Ticket** or **Update Ticket** tool. See [Automations](https://www.tryrisotto.com/docs/dashboard/automations#tools-available-to-the-agent).
- A runbook sets it with the [Update Ticket](https://www.tryrisotto.com/docs/dashboard/tools#update-ticket) tool. Add the tool to the runbook, and name the field and the value in the runbook instructions.

### Managing fields with the Assistant

Ask the dashboard assistant to create additional fields or list the ones already defined for a department. It can also set additional field values when creating or updating a ticket on your behalf.

> **Note:** Editing an existing field, toggling it active, and deleting a field are only
> available from this settings page.

### Syncing field values to Jira or ServiceNow

A department that syncs tickets to Jira or ServiceNow can push its additional field values to the external issue. After you map a field, the sync is automatic. You do not add anything to a runbook to send the value.

The sync is outbound only. A value changed in Jira or ServiceNow does not come back to the Risotto ticket.

Risotto sends the mapped values at these times:

- **When it creates a Jira issue.** The values are part of the create request, so they can fill fields that your Jira project requires.
- **When a field value changes.** A few seconds after the change, Risotto updates the external issue.
- **When it syncs any other change.** For example, a status or assignee change also sends the current values.

ServiceNow does not get the values in the create request. It gets them with the first update after Risotto creates the record.

Risotto sends a field only if the ticket has a value for it:

- A field that nobody set is not sent. The value in Jira or ServiceNow stays as it is.
- A field that someone cleared is sent as empty. Risotto clears it in Jira or ServiceNow too.

On an update, Risotto sends the field values in a separate request. If Jira or ServiceNow rejects a value, Risotto logs the error. The other changes to the external issue still sync. For example, Jira rejects a value for a field that is not on the issue's edit screen.

1. **Open the integration's settings**

   Go to **Settings > \<department> > Ticket Sync**. On the Jira or ServiceNow card, open the **Connected** menu and click **Configure...**.

2. **Map each field**

   In the **Additional Fields Mapping** section, pick the Jira field or ServiceNow column for each Risotto field you want to sync. A field without a mapping is not synced. On a first-time connection the section is not shown yet: click **Save**, then open **Configure...** again to map the fields.

3. **Map each dropdown choice**

   Under a mapped dropdown field, a chip such as **2/3 mapped** counts the choices that have a value in the external system. Expand it and pick the external option for each choice. Choices whose label or value matches an external option are filled in for you, and the row says how many matched automatically. Pick **Not mapped** to clear one.

4. **Save the mapping**

   Click **Save**. When Risotto can read the external field's option list, the dialog refuses to save while a choice is unmapped or a mapped value is not one of those options, and it names the choice. When it cannot read the list, you type the exact external option value and the dialog only warns.

Which Risotto field types sync depends on the target. Jira takes every type except **Checkbox**. ServiceNow takes every type. The mapping section hides fields of a type the target cannot take.

> **Note:** The Jira field picker lists your site's global custom fields. A custom field
> that belongs to one team-managed project is not listed, so it cannot be mapped
> yet. Searching for it shows **No Jira fields match.**

### Reporting

Additional fields are available in the ticket list as optional columns and filters:

- Show a field via the ticket list's column picker or filters, the same way you would for a built-in field
- **Download current view as CSV** includes only the additional field columns you've added to the view; **Download all fields as CSV** includes every additional field automatically

See [Ticket Inbox](https://www.tryrisotto.com/docs/dashboard/tickets/all) for more on filtering, columns, and CSV export.

### Deactivating and deleting fields

Turn off a field's **Active** switch to hide it from tickets and reports without losing data — existing values are kept, and you can turn the field back on later.

To delete a field, click its trash icon, then click **Save changes**. There is no confirmation.

> **Warning:** Deleting a field (rather than deactivating it) permanently deletes it along
> with every value stored on tickets for it. This cannot be undone.

## Members

Members can view and manage requests sent to this department. Open **Settings > \<department> > Members**.

### Adding members

Org Admins and the department's Supervisors can add and remove members.

1. **Open the member picker**

   Click **Add a member**. The picker lists the people in your organization who are not in the department yet.

   *Product example: A department's Members card in the Risotto dashboard, with Add a member open on the org's members.*

2. **Pick the person**

   Search for the person and click them. They join the department as an **Agent**.

To add someone who is not in your organization yet, click **Invite member** in the picker. See [Invite Users to Organization](https://www.tryrisotto.com/docs/guides/invite-users).

To change a member's role, pick **Agent** or **Supervisor** in their **Role** select, then click **Promote** or **Demote** to confirm. To remove a member, open the **⋮** menu on their row, click **Remove**, then click **Confirm**. On your own row, the item is **Leave**.

A member added by directory sync shows a lock instead of the **⋮** menu. To remove them, remove them from the group in your identity provider. You can still change their role. When your organization uses directory sync, Org Admins see a **Directory Sync** card on the page: members of the identity provider groups listed there join the department as agents.

On a sub-department's **Members** page, the members of the parent department are listed too, with their role in the parent, such as "IT Supervisor".

### Member roles

> **Tip:** See [Permissions](https://www.tryrisotto.com/docs/operating/permissions) for detailed information about
> roles and their specific permissions

- **Agent**: Can read and update tickets, view analytics and settings, but cannot delete tickets or modify department settings
- **Supervisor**: Has full department control including ticket deletion and settings management

## Danger zone

The **Danger zone** section is at the bottom of the settings page of the department. To open it, click the department under **Departments** in the Settings sidebar.

### Make default department

A top-level department that is not the default has a **Make Default…** button. Click it, then click **Confirm** in the **Change Default Department?** dialog. Risotto then sends new tickets that match no department to this department. Existing tickets stay in their current departments. New departments start with the default department's settings. A sub-department cannot be the default, so it has no **Make Default…** button.

### Delete department

Only Org Admins and Managers can delete a department.

1. **Start the deletion**

   Click **Delete Department…**.

2. **Confirm**

   Click **Confirm** in the **Delete Department?** dialog. When the department has sub-departments, the dialog says that they are deleted too. Risotto then opens Settings.

   *Product example: The Delete Department? confirmation over the Finance department's Danger zone, and Confirm.*

> **Warning:** Deleting a department will remove all its configuration and member
> assignments, and deletes its sub-departments with it. Its tickets move to its
> parent department, or, for a top-level department, to the default department.
> This action cannot be undone.

Only delete departments that are no longer needed. Consider moving any active requests to other departments before deletion.

An integration connection belongs to one department, even when it serves the whole organization. Often this is the department that was the default when you connected it. When you delete a department, Risotto moves the connections it owns, for example Slack, Slack Tools, Jira, Confluence, or Guru, to another department, so they keep working for the rest of the organization. They go to the department that receives the deleted department's tickets, or to another department if that one already has a connection of the same type. The confirmation dialog shows **This department owns org-wide connections** and names those connections.

- If another department already has the same connection, Risotto keeps that one and deletes the duplicate.
- If no other department can take a connection, Risotto deletes it, and you must reconnect the integration.

Risotto also deletes the indexes, runbooks, and additional ticket fields of the department, and removes its articles. Move or recreate anything you want to keep before you delete the department. The tickets of the department are not deleted.

You cannot delete the default department. The **Delete Department…** button is disabled, with the tooltip "Default department cannot be deleted. Make another department default first."

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