# Search table macro

The table macro renders a saved search on a page. Because it points at the saved search rather than copying it, the page updates when the search does.

It renders for unlicensed and anonymous readers, which makes it usable on public pages and published sites.

---

## Settings

| **Setting**                                                                                    | **What it changes**                                                                                                                                                                                      |
| ---------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Search Mode                                                                                    | Chooses whether the macro points at a stored saved-search asset ('Saved' reveals the Saved search picker) or carries its own query ('Custom' reveals the Filter Mode / filters / CQL block).             |
| Filter Mode                                                                                    | Basic builds the query from filter chips; CQL hands you a raw CQL editor. Description shown: 'Choose how to define your custom filters.'                                                                 |
| Columns / Custom Columns                                                                       | Overrides which columns the table shows. The field is titled 'Custom Columns' with description 'Override the configured columns' in Saved mode, and 'Columns' / 'Choose which columns to display' in Cus |
| Sort / Sort order / Limit / Column order / Column widths (inside the stored \`search\` object) | Sort and sort order ARE editable (through the Sort dropdown in Basic mode). Limit is written by the schema but overridden by Page Size whenever Page Size is set. columnOrder/columnWidths are only ever |
| Search Mode                                                                                    | Chooses whether the Search / Search Cards macro renders a saved search or an ad-hoc query.                                                                                                               |
| Custom Columns                                                                                 | In saved mode the label changes to 'Custom Columns' / 'Override the configured columns', the macro can display different columns from the ones stored on the saved search without changing the saved se  |
| Page Size                                                                                      | Sets how many results the macro requests from Confluence. On the table this is the rows-per-page. On the cards it is only the fetch size, cards always show 12 per page client-side.                     |
| Sort / Sort order / Limit / Column order / Column widths (inside the stored \`search\` object) | Sort and sort order ARE editable (through the Sort dropdown in Basic mode). Limit is written by the schema but overridden by Page Size whenever Page Size is set. columnOrder/columnWidths are only ever |
| Search table (Capable) / Search table macro (Capable)                                          | Renders a saved search as a table on a page. Available to unlicensed and anonymous viewers in both apps.                                                                                                 |
| Search cards (Capable) / Search cards macro (Capable)                                          | Renders a saved search as cards. Same visibility rules as the table macro.                                                                                                                               |
| Search Mode                                                                                    | Chooses whether the macro points at a stored saved-search asset ('Saved' reveals the Saved search picker) or carries its own query ('Custom' reveals the Filter Mode / filters / CQL block).             |
| Saved search                                                                                   | Points the macro at a stored saved search; the macro then renders that asset's CQL/filters, columns and limit. Updating the saved search updates every macro pointing at it.                             |

ℹ️

**Search Mode decides where the query comes from.** Saved points the macro at a stored saved search. The alternative builds the query on the macro itself, which is useful for a one-off but harder to maintain.

---

## A few things worth knowing

* Pointing several pages at one saved search is the whole point. Change it once, every page follows.
* Deleting the saved search leaves the macro with nothing to render.
* Page size is what the macro requests, not what Confluence necessarily returns.

---

## Related

[Search cards macroThe same, as cards.](https://help.gocapable.com/search/search-cards-macro.html)

[Working with saved searchesWhat it points at.](https://help.gocapable.com/search/working-with-saved-searches.html)

[Searching ConfluenceBuilding the query first.](https://help.gocapable.com/search/searching-confluence.html)

---

_Points at the search. Follows the search._