Who this article is for: Admins configuring homepage cards, and all users who open data from the homepage.
Permissions required: Configuring a card requires Organization Admin access. Once set, all users benefit from the scoped view when they open the card.
Homepage cards give you an at-a-glance view of your architecture data and a one-click way to manage it. This usability upgrade lets admins tailor each card's Manage Data experience — scoping which records are counted, and setting the filters, columns, and sorting users see. The card's total count then matches the data that actually matters, so the homepage stays trustworthy. Users land on the right view in one click instead of re-filtering the inventory every time.
Prefer to follow along? Take the interactive step-by-step tour, or watch the full walkthrough at the end of this article.
Why This Matters
Previously, a homepage card counted and displayed all records of its component type, including irrelevant ones such as retired applications, and every user had to re-apply the same filters in the inventory to focus on what they needed. Now you configure the scope once, in Homepage Settings. The card's total count reflects only the records you choose to include, and clicking Manage Data opens the inventory pre-configured with the filters, columns, and sorting you set. This turns roughly four or five clicks into one.
How to Configure a Card's Scope, Columns, and Sorting
1. Go to Homepage Settings
Press Command + K (Mac) or Ctrl + K (Windows), search for Organization Settings, and open Homepage Settings. This is where you control what data the card includes and how it is presented.
2. Scope the Card's Count
Exclude records that should not be counted — for example, uncheck retired applications so the card total reflects only active data. Click Save to apply the configuration.
3. Configure Filters, Columns, and Sorting
The data settings let you define exactly what the inventory shows, and in turn what the card reflects:
Filters — narrow to the records users should see, for example by lifecycle, criticality, or a reference condition.
Columns — show the attributes that matter and hide the ones that do not.
Sorting — order the records so the most important appear first.
Click Edit settings to open the inventory drawer directly and adjust the view without leaving the configuration flow. In the walkthrough, for example, we hide the Owners column, add Consumes Reference, and set Criticality to hide empty values and sort in descending order.
4. Save the Scoped View
Save your configuration. From now on, the homepage card reflects the scoped dataset you defined, and every user who clicks Manage Data lands on exactly the filters, columns, and sorting you set.
Example Use Cases
Retire the noise: exclude retired or phased-out applications so the card counts and shows only live systems.
Surface what is critical: sort by Criticality in descending order and hide empty values so high-impact records rise to the top.
Focus the columns: hide broadly-owned or empty columns such as Owners, and add the fields your users act on, like Consumes Reference.
Best Practices
Match each card to a real workflow. Scope the card around the question users ask when they open it, not around all available data.
Test in a sandbox first. If available, validate your configuration in a sandbox environment before rolling it out to the whole organization.
Keep the count trustworthy. The value of the upgrade is that the number on the card matches reality, so exclude records that would mislead users at a glance.
Known Limitations
Organization-wide configuration. Scope, columns, and sorting are configured by admins at the organization level and apply to all users who open the card. They cannot currently be tailored per role, group, or individual.
One configuration per card. Each card holds a single scoped view. To offer a different slice, use a separate card.
Frequently Asked Questions
Do I Need Admin Rights to Use This?
You need Organization Admin access to configure a card. Once saved, all users benefit from it when they open the card, with no extra permissions required.
Will This Change My Existing Homepage Cards?
No. Existing cards keep working as before. Scoping a card is optional and only affects the cards you choose to configure.
Does the Card's Total Count Change Too?
Yes. When you exclude records from the scope, the card's total count updates to reflect only the included data.
Can Each User Set Their Own Filters, Columns, or Sorting?
Not currently. The configuration is set at the organization level and shared by all users who open the card.
What's Next
Feel free to reach out to us via the in-app chat if you have any follow-up questions about this article. If you would like to learn more about the homepage, check out these related articles:
Want to help shape where this feature goes next? Follow its progress and share feedback on our product portal: Homepage Cards: Filter Your Data Inventory via Manage Data.
You can also follow the interactive tour or watch the video walkthrough.