Cards

Show contextual information about a ticket’s requester in the ticket sidebar with cards, provided either by Ravenna or by a connected integration.

Cards surface context about a ticket’s requester directly in the ticket sidebar, so agents can triage without leaving the ticket. Ravenna provides one card of its own, and 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, with the Ravenna group first, then a group for each connected integration.

Card	Provided by	Shows	Sidebar section
Assets	Ravenna	Assets assigned to the requester	Assets
Requester Info	Okta, Rippling	The requester’s identity or employment record	Requester
Requester Endpoints	Fleet, Jamf Pro, JumpCloud, Microsoft Intune, Iru	Devices assigned to the requester	Devices

An integration’s cards only appear on the settings page once the integration is connected. Disconnecting it removes its group again. The Assets card needs no integration and is available to every organization.

---

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 Assets, 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.

Header control	Behavior
Refresh	Clears the card’s cached data and fetches it again.
Provider link	On Requester Info cards, opens the requester’s record in Okta or Rippling in a new tab.

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.

The Assets card is not cached. It reads Ravenna’s own records, so an edit to an asset shows on the next load.

---

Assets card

The Assets card lists the assets assigned to the ticket’s requester, up to five of them. Each asset renders as a block headed by the asset name, with the fields you chose to show listed inside it.

Field	Description
Name	The asset name, used as the heading of the asset’s block. Shown by default.
Type	The asset type. Shown by default.
Description	The asset description.
Created	The date the asset was created, as an absolute date.
Updated	When the asset was last updated, as relative time.

Every custom asset field your organization has defined is also available, listed after the built-in columns. How a custom field renders depends on its type:

Field type	Rendered as
Text, Number	Plain text.
Date	An absolute date, so a warranty expiry reads as a date rather than “in 2 years”.
Select	A badge.
Multi Select	A single badge listing the selected values.
Boolean	Yes or No.
User	The matching organization member, or the raw value when no member matches.

A field with no value for a given asset is left out of that asset’s block rather than shown empty, so two assets of the same type can list different fields.

---

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:

• Fleet
• Iru
• Jamf Pro
• JumpCloud
• Microsoft Intune

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.