Context
Choose which details about people and devices the support agent can see while it works a ticket, and test what it sees about you
The Context page controls what the support agent can see about the requester, the people a request is about, and their devices while it works a ticket. Tools return only the fields that you select here. Changes apply from the next run of the agent.
To open the page, go to Settings and click Support agent. The Context page opens. Org Admins and Managers can view and change the page. Anyone else who opens it sees every control locked, and the page shows Only admins can change these settings.
How the page works
The page has four tabs: Identity, People, Devices, and Knowledge. Each of the first three tabs shows a status dot. Point to the tab to see its status:
- On (green): the lookup is on. Identity is on when an identity provider is connected. People and Devices are on when their Agent access switch is on.
- Off (grey): the Agent access switch is off.
- Not connected (grey): no provider is connected.
The Knowledge tab has no status dot. Inside each of the first three tabs, a card shows the connected provider and Connected. If no provider is connected, the card is grey, its controls are disabled, and a button takes you to the integrations catalog:
| Tab | Data source | Button when not connected |
|---|---|---|
| Identity | Identity provider | Connect an identity provider |
| People | HR system | Connect an HR system |
| Devices | MDM | Connect an MDM |
The field tables on the Identity and People tabs have the columns Field, Key, Sample value, and Visible to agent. Above each table:
- All, Visible to agent, and Hidden from agent filter the rows. Each one shows its count of fields.
- Search fields finds a field by its name or its key.
There is no Save button. Each switch saves when you change it, and the page shows Saving... and then All changes saved. If a save fails, the page shows Couldn't save the change. The page shows the saved value. and puts the saved value back.
The settings apply to the whole organization. You cannot set them per department.
The What the agent sees panel on the right shows a sample lookup for one made-up person, with the fields that the agent gets for the open tab. Real values come from your own systems. Under the open tab's lookup, Other lookups lists the other lookups with their field count or their status. On the Knowledge tab, the panel shows only the list of Lookups, because knowledge search has no sample.
Test as me
To see what the agent gets about a real person, click Test as me in the panel. Risotto runs the agent's lookups for your own email against your identity provider, HR system, and MDM, with the settings on the page. The panel shows Testing... while the lookups run, then A real lookup for your email.
- Each lookup shows its result: the profile from the identity provider, the employee record, and your devices. On the Devices tab, the panel lists each device that the agent finds. The agent gets the details of one device in a separate lookup.
- When a lookup returns nothing, the lookup shows a badge and a sentence that tells you why: Off, Not connected, Not found (for example, your HR system has no employee record for your email), or Error (check the connection, then test again).
- When you change a setting, the panel runs the test again after the change saves.
- Click Show sample to go back to the made-up person.
The test runs only when you click Test as me, and it uses only your own email. If the test fails, the panel shows Couldn't run the test. and a Try again button. If you test too often, the panel shows Too many tests. Wait a minute, then try again.
Identity
The Identity tab controls the profile fields from your identity provider that the agent sees about the requester and about anyone a request is about. The tab has no on or off switch. It is on when an identity provider is connected.
- Name and Email are always shared. They show a lock icon. The agent also always gets the person's Risotto identity ID and pronouns, which are not in the table.
- Use the switch in the Visible to agent column to share or hide each other field.
- A field marked If in your profile is an Okta custom attribute. Okta returns it only if your Okta user profile has it.
- The page shows one table for each provider. A field appears only under the providers that return it. If a field appears in two tables, one switch controls both.
- If you connect more than one provider, the agent reads profiles from one provider only. That table shows Used by agent. The other tables say that their fields don't reach the agent.
Hiding a field changes only what the agent sees. Access rules and approver routing still read every built-in profile field.
Custom fields
You can share a field from your identity provider that is not in the built-in list, for example a badge number or a cost code.
Open the Identity tab
Go to Settings, click Support agent, and open the Identity tab.
Add the field
Click Add custom field, next to the Search fields box. The Add custom field dialog opens.
Enter the key and the label
In Key, enter the name of the field as your identity provider stores it (see the table below). The dialog shows where to find the key in the provider that the agent reads. In Label, enter the name that the page shows. The agent sees the key and its value, not the label.
Save the field
Click Add field. The dialog closes, and a message says Added Employee number. Turn it on to share it with the agent., with the label of your field.
The field appears at the end of the table with a Custom marker. A new field is off. Turn on its switch in the Visible to agent column. The agent gets the field from its next run.
| Provider | Key to enter |
|---|---|
| Okta | The variable name of the attribute (Directory > Profile Editor, then the user profile). For example, employeeNumber. |
| Microsoft Entra ID | The Microsoft Graph property name. For example, employeeId, extensionAttribute1 to extensionAttribute15, or extension_<appId>_<name> for a directory extension. |
| Google Workspace | schema.field: the name of the custom schema, a dot, and the name of the field. For example, employmentData.badgeNumber. A field with many values gives a list of every value. |
| JumpCloud | The name of the custom attribute (User Management > Users, then a user). For example, costCode. |
Rules for custom fields:
- You can add up to 20 custom fields. When you have 20, Add custom field is disabled. Remove a field to add another.
- A key has 128 characters or fewer. It uses letters, digits, and underscores, or
schema.fieldfor Google Workspace. - A label has 64 characters or fewer.
- A key cannot be the same as a built-in field, another custom field, or a key that the agent always gets, such as
identity_idorpronouns. The check is case-sensitive. The dialog names the field that already uses the key. - To remove a custom field, click the trash icon on its row. There is no confirmation.
If the save fails, the dialog stays open and shows Couldn't add the field. with the reason.
If the key does not fit the provider that the agent reads, the row shows a note, for example Okta doesn't return this key. The agent gets no value for that field.
Access rules and approver routing do not use the Visible to agent switches. For Okta, Google Workspace, and JumpCloud, they can read a custom attribute that is not shared. For Microsoft Entra ID, they read only the built-in fields.
People
The People tab controls the employee record from your HR system.
- Turn on Agent access to let the agent look up the requester's employee record. When Agent access is off, the agent cannot look up the record, and its instructions do not mention it.
- ID, Descriptor, and Email are always shared.
- Use the switches to share or hide Business Title, Hire Date, Supervisory Organization, Work Location, Job Profile, and Worker Type. HiBob, BambooHR, and Rippling do not return Job Profile or Worker Type.
- Supervisory Organization, Work Location, Job Profile, and Worker Type each have an ID and a name. Their key ends in
_*, for examplejob_profile_*, and one switch shares both. - The agent never sees compensation.
The agent can look up only the requester's own record. Time off and home address requests are not on this page. They use the HR runbook templates in Runbooks > Templates (see Runbooks). The old People Actions page (Settings > People > Actions) is gone. Its old link opens the runbook templates.
Devices
The Devices tab controls device lookups from your MDM.
- Turn on Agent access to let the agent look up the devices assigned to the requester and the details of each device. When Agent access is off, the agent cannot look up devices.
- You cannot select device fields. The Visible to agent column shows Always for every field. When Agent access is on, the agent sees every field in the table, for example Device Name, Model, Serial Number, OS Version, and Last Check-In.
- If you connect more than one MDM, the agent reads devices from all of them. The MDM field shows which MDM reported each device. Fields that only some MDMs return show the name of those MDMs.
Knowledge
The Knowledge tab is read-only. It lists the indexes whose audience is Everyone, because these are the indexes that the support agent can search. The Searched for column shows Every requester, or Some requesters when a profile rule filters the index by who asks. A line above the list sums this up. If no index has the audience Everyone, the tab says that the support agent has no knowledge to search.
Click View indexes to go to the indexes, where you can change an index's audience with Configure.... Profile filters are set when you create an index and can't be changed afterwards.
Defaults
For a new organization, Agent access is off on the People and Devices tabs, and every built-in field is shared. There are no custom fields. If your organization had Get Employee Info on under People Actions, or Get Device Info on under Device Actions, the matching Agent access switch is on.
Something wrong or missing? Report an issue · View as Markdown