> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# 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. Each connected integration can add cards backed by its own data.

## Mental model

A card is a read-only panel in the ticket sidebar, resolved from the ticket's requester. Every card is registered by the integration that provides it, and configured once per organization.

Two independent settings control a card:

| Setting            | Level         | Controls                                                               |
| ------------------ | ------------- | ---------------------------------------------------------------------- |
| Enabled workspaces | Per workspace | Which workspaces render the card on their tickets.                     |
| Visible fields     | Organization  | Which fields each card entry lists. Shared by every enabled workspace. |

A card is only listed when the integration that provides it is connected to the organization.

***

## Card catalog

| Card                | Provider                                          | Context   | Field configurable | Cached | Sidebar section |
| ------------------- | ------------------------------------------------- | --------- | ------------------ | ------ | --------------- |
| Requester Info      | Okta, Rippling                                    | Requester | Yes                | Yes    | Requester       |
| Requester Endpoints | Fleet, Jamf Pro, JumpCloud, Microsoft Intune, Iru | Requester | No                 | Yes    | Devices         |

Cards hold their results for up to an hour, keyed by workspace and card context. The refresh control in the card header drops that entry and refetches.

***

## Constraints and gotchas

* Configuring cards requires organization admin access.
* The visible field selection is organization-wide, not per workspace. Only enablement is scoped to a workspace.
* **Requester Endpoints** cards expose no field selection at all, so their fields cannot be trimmed.
* A card that fails to resolve its data renders as empty rather than surfacing an error, so an empty card can mean either no data or a failed provider call.
* A requester with nothing to show renders **No data found** instead of hiding the card.
* A field with no value on a given entry is omitted from that entry rather than rendered empty, so entries in the same card can list different fields.


## Related topics

- [Cards](/integrations/rippling/cards.md)