Skip to main content
Cards surface context about a ticket’s requester directly in the ticket sidebar, so agents can triage without leaving the ticket. Each connected integration can add cards backed by its own data.

​
Available cards

You manage every card in one place: Settings > Organization - Cards. Cards are grouped by whatever provides them, one group per connected integration.
An integration’s cards only appear on the settings page once the integration is connected. Disconnecting it removes its group again.

​
Enable a card

1

Open card settings

Go to Settings > Organization - Cards. You need organization admin access.
2

Choose workspaces

Under Enabled Workspaces, select which workspaces show the card on their tickets. The card only renders on tickets in the workspaces you select.
3

Choose visible fields

Cards that support it also have a Visible Fields list. Toggle on the fields you want the card to show and leave the rest off.
Both selections save when you click outside the list.
Field selection is organization-wide. Every workspace with the card enabled shows the same fields, so turning a field off hides it everywhere. Only enablement is per workspace.
Requester Endpoints cards have no Visible Fields list. They always show the device fields their integration provides.

​
Cards on a ticket

Each enabled card renders as its own section in the ticket sidebar. Card sections are ordered Requester, then Devices.A card from an integration is titled with its provider, for example Requester Endpoints (Jamf Pro). A Requester Info card shows the requester in place of a title, so you can open their profile from the card header.If there is nothing to show for the requester, the card renders No data found rather than hiding itself.

​
Data freshness

Integration cards cache their results for up to an hour per workspace and requester, so opening several tickets for the same person does not re-query the provider. Use Refresh in the card header after you change something in the source system.

​
Integration cards

Integrations register their own cards when connected, and each appears as its own group on the same settings page. Two kinds exist today.Requester Info resolves the requester to a user in the provider’s directory and shows that record. Fields differ by provider, so see the card documentation for each:
  • Okta for identity and profile attributes
  • Rippling for employment attributes
Requester Endpoints shows the devices assigned to the requester, with the device fields the provider reports:An organization can enable more than one of these at once. Each connected provider contributes its own card section, so a requester with a Jamf-managed laptop and a JumpCloud-managed workstation gets a section for each.
Last modified on September 16, 2026