Hi @eyalabuhame ,
The screenshot appears to be from the Workplace Reservation Management (WSD) portal.
Whether you can add more information to the reservation cards depends on what you're trying to display:
Configuration (OOTB)
The card content is driven by data from the underlying Space records.
Check the configured card views and view rules used by the WSD portal.
If the information already exists in standard fields (for example: location, capacity, amenities, or description), you may be able to expose it through configuration without any customization.
Customization
If you need to display custom fields or change the card layout, you'll need to customize the underlying component/widget.
For Service Portal: Clone the relevant widget and update the server script and template. (Tip: If fetching any data dynamically from the client side, ensure you use Asynchronous GlideAjax to maintain optimal load performance).
For Employee Center or UI Builder: Clone the component and update the data binding and layout accordingly.
Architectural Best Practice: Avoid modifying OOTB components directly. Instead, create a cloned version with your organization's naming convention (for example, DOTS-WSD-Search-Card) so future upgrades are easier to manage and your custom elements are immediately identifiable.
Could you share which additional information you'd like to display on the card? That will help determine whether this can be achieved through configuration or requires customization.
Please mark this answer as Helpful if it resolves your question. 🙂
Thanks,
Yogesh Bhatt
