Filters & Default Filters

Every list in SDA — devices, projects, pipelines, jobs, documents, vulnerabilities, users — can be narrowed with the filter buttons above the table. Normally a selection lasts only for the current visit: leave the page, come back, and the list is unfiltered again.

Default filters make a selection stick. Once you save one, that list opens with the filter already applied — every time, from any browser you sign in from.

A list opens with its default filters already applied.

The two layers

Layer	Who can set it	Who it applies to
Personal default	Any user, for their own account	Only you
Company default	Users with permission to update the company settings	Everyone in the company who has not set a personal default for that filter

Defaults are stored per list and per filter. A default on the Status filter of the device list has no effect on the Status filter of the pipeline list, so you can tune each page independently.

When a list loads, SDA resolves each filter in this order and uses the first value it finds:

1. Your personal default

2. Your company's company default

3. The platform baseline that ships with SDA

A link that already contains filters in its address wins for that visit — so a filtered view you share with a colleague still opens exactly as you sent it, whatever defaults either of you has saved.

Saving a default

1. Open any filter above a list and choose the values you want.

2. Save appears in the row of actions inside the filter. It is only there while your current selection differs from the default already in effect.

3. Click Save.

Save appears as soon as your selection differs from the current default.

If you are allowed to change company settings, Save opens a short menu instead of saving straight away:

• Set current as my default — stores it for your account only.

• Set current as company default — stores it for everyone in the company.

With permission to change company settings, you choose which layer to write to.

Everyone else simply gets the personal default saved on click. Either way a short confirmation appears while the preference is stored, and the list you are looking at is already showing the selection you just saved — nothing reloads.

Saving "show everything" as a default

Some lists ship with a baseline filter — for example, hiding archived entries. Clearing the filter completely and then saving stores no filter as your default, so the list opens showing everything. This is a real saved value, not the absence of one: it overrides the platform baseline just like any other default.

Seeing and removing a default

When a saved default is in effect, the bottom of the filter tells you which layer it came from:

• Using personal default filter

• Using company default filter

Each filter states which layer its default comes from.

Remove next to that line deletes the default. What you fall back to depends on which layer you remove:

You remove	The filter then falls back to
Your personal default	The company default, if there is one — otherwise the platform baseline
The company default	The platform baseline

If both a personal and a company default exist and you can change company settings, Remove opens a menu so you can pick which one to delete.

With both layers set, choose which default to remove.

A personal default always beats the company default. If your administrator sets a company default and the list does not change for you, you already have a personal default on that filter — remove it to follow the company setting.

Reset, Clear and Save

Three actions sit in the same row inside a filter, and they do different things:

Action	Effect
Clear	Deselects everything in this filter, for this visit only
Reset	Returns this filter to its current default, for this visit only
Save	Makes your current selection the default from now on

Reset filters above the table does the same as Reset, for every filter on the page at once. None of these change a saved default except Save.

What can be saved as a default

Default filters cover the dropdown filters above a list — status, type, group, tag, user, and so on.

They deliberately do not cover:

• free-text search

• column sorting

• time-range selectors

• rows per page

• table and view toggles

Group, tag and user filters

The group, tag and user filters can be saved as a personal default, but not as a company default. Their options depend on what each user is allowed to see, so a single company-wide value would mean different things — or nothing at all — for different colleagues. In those filters the company option is shown but not selectable, with the note Not available for permission-restricted filters.

Where default filters are available

Anywhere SDA shows a filtered table, including:

• Devices and their job tabs — backups, deployments, restores

• Projects, project versions, libraries and linked versions

• Documents

• Pipelines and their jobs

• SDA Gateways

• Integrations and Custom fields

• Licenses and Workstations

• Vaults

• Security Hub vulnerabilities

• Browser-based engineering recordings and session history

• Users, Roles and Audit logs

See also

• Groups & Tags

• General Settings — setting a company-wide default