FLINT TABLE FILTER · HOW-TO
Publish shared table views for different teams
One tracker, several audiences. Instead of copying the table for each team, publish named views on the page that any reader can apply.
What you will end with: three shared views in every reader’s Reader view list: Engineering (7 open tasks), Support (4 tasks) and Review (3 tasks in review, grouped by team). The page still opens on the author’s starting view.
Defaults, shared views and personal views
| Author defaults | Shared views | Personal views | |
|---|---|---|---|
| Created by | Page author, in macro settings | Page author, from a prepared view | Any reader |
| Stored in | The page’s macro settings | The page’s macro settings | The reader’s browser |
| Applied | When the page opens and after Reset view | When a reader chooses one and Apply view | When that reader chooses one and Apply view |
| Visible to | Everyone who can read the page | Everyone who can read the page | Only that reader, in that browser |
Use defaults for the view most people need first, and shared views for the alternatives. Readers can apply a shared view, adjust it and save the result as their own personal view.
Before you start
You need permission to edit the page. This guide uses the project tracker from the weekly status review.
Sample tracker: project-tracker.csv · 24 rows, 7 columns, fictional data.
| Task ID | Task | Team | Owner | Status | Due | Estimate |
|---|---|---|---|---|---|---|
| PRJ-101 | Checkout API timeout fix | Engineering | Priya Shah | Blocked | 2026-11-06 | 3 |
| PRJ-102 | Billing page redesign | Design | Mateo Ruiz | In progress | 2026-11-12 | 5 |
| PRJ-103 | Release notes draft | Docs | Hana Sato | To do | 2026-11-13 | 2 |
| PRJ-104 | Search index migration | Engineering | Liam O'Neill | In progress | 2026-11-10 | 8 |
Show all 24 rows
| Task ID | Task | Team | Owner | Status | Due | Estimate |
|---|---|---|---|---|---|---|
| PRJ-101 | Checkout API timeout fix | Engineering | Priya Shah | Blocked | 2026-11-06 | 3 |
| PRJ-102 | Billing page redesign | Design | Mateo Ruiz | In progress | 2026-11-12 | 5 |
| PRJ-103 | Release notes draft | Docs | Hana Sato | To do | 2026-11-13 | 2 |
| PRJ-104 | Search index migration | Engineering | Liam O'Neill | In progress | 2026-11-10 | 8 |
| PRJ-105 | Help center screenshots | Docs | Hana Sato | Done | 2026-11-04 | 1 |
| PRJ-106 | Support macro update | Support | Ama Mensah | In review | 2026-11-11 | 1 |
| PRJ-107 | Launch email copy | Marketing | Jonas Berg | In progress | 2026-11-20 | 2 |
| PRJ-108 | Accessibility fixes | Design | Mateo Ruiz | Blocked | 2026-11-18 | 4 |
| PRJ-109 | Rate limit alerts | Engineering | Priya Shah | To do | 2026-11-14 | 3 |
| PRJ-110 | Escalation runbook | Support | Ama Mensah | In progress | 2026-11-27 | 2 |
| PRJ-111 | Pricing FAQ | Docs | Lena Fischer | In review | 2026-11-09 | 1 |
| PRJ-112 | Webhook retry policy | Engineering | Liam O'Neill | Blocked | 2026-11-24 | 5 |
| PRJ-113 | Customer webinar plan | Marketing | Jonas Berg | To do | 2026-12-02 | 3 |
| PRJ-114 | Status page wording | Support | Ama Mensah | Done | 2026-11-05 | 1 |
| PRJ-115 | Mobile layout review | Design | Noor Haddad | To do | 2026-11-15 | 2 |
| PRJ-116 | Data export test plan | Engineering | Priya Shah | In review | 2026-11-12 | 2 |
| PRJ-117 | Partner briefing deck | Marketing | Jonas Berg | Blocked | 2026-11-13 | 2 |
| PRJ-118 | API changelog | Docs | Lena Fischer | To do | 2026-11-19 | 1 |
| PRJ-119 | Trial onboarding emails | Marketing | Sofia Costa | In progress | 2026-11-16 | 3 |
| PRJ-120 | Dependency upgrades | Engineering | Liam O'Neill | To do | 2026-11-23 | 5 |
| PRJ-121 | Ticket tag cleanup | Support | Tomás Silva | To do | 2026-11-17 | 1 |
| PRJ-122 | Icon refresh | Design | Noor Haddad | Done | 2026-11-02 | 2 |
| PRJ-123 | Backup restore drill | Engineering | Priya Shah | To do | 2026-11-30 | 3 |
| PRJ-124 | Glossary update | Docs | Hana Sato | In progress | 2026-11-26 | 1 |
Step 1: Prepare the Engineering view
Build the view on the published page, exactly as readers should receive it.
- Filter Team to Is one of Engineering and Status to Is not one of Done.
- Choose Columns and clear Team. Sort Due ascending.
- Open Saved views and presentation, enter
Engineeringin View name and choose Prepare shared view settings. - The status reads Copy the settings into Shared reader views in the macro settings, then publish the page. Select everything in Shared reader views settings and copy it.
Step 2: Publish it
- Edit the page and open the Flint Table Filter macro settings.
- Set Settings section to Shared reader views.
- Replace the entire contents of Shared reader views with the copied text. Choose Save settings, then publish the page.
Preparing a view never edits the page; only publishing the macro settings does.
Step 3: Add Support and Review
The prepared text contains every shared view already published plus the new one, which is why you replace the field each time. Prepare the next view only after the previous one is published.
- Reload the published page and choose Reset view. Filter Team to Support, clear Team in Columns and sort Due ascending. Prepare it as
Support, then paste and publish as before. - Reload and reset again. Filter Status to Is one of In review and sort Due ascending. In Summary, set Group rows by to Team. In Saved views and presentation, select Group rich rows with subtotals. Prepare it as
Review, then paste and publish.
What readers get
Readers open Saved views and presentation and see Author default, Shared: Engineering, Shared: Support and Shared: Review in Reader view, followed by any personal views of their own. Applying a view starts at page one.
| Task ID | Task | Owner | Status | Due |
|---|---|---|---|---|
| PRJ-101 | Checkout API timeout fix | Priya Shah | Blocked | 2026-11-06 |
| PRJ-104 | Search index migration | Liam O'Neill | In progress | 2026-11-10 |
| PRJ-116 | Data export test plan | Priya Shah | In review | 2026-11-12 |
| PRJ-109 | Rate limit alerts | Priya Shah | To do | 2026-11-14 |
| PRJ-120 | Dependency upgrades | Liam O'Neill | To do | 2026-11-23 |
| PRJ-112 | Webhook retry policy | Liam O'Neill | Blocked | 2026-11-24 |
| PRJ-123 | Backup restore drill | Priya Shah | To do | 2026-11-30 |
| Task ID | Task | Owner | Status | Due |
|---|---|---|---|---|
| PRJ-114 | Status page wording | Ama Mensah | Done | 2026-11-05 |
| PRJ-106 | Support macro update | Ama Mensah | In review | 2026-11-11 |
| PRJ-121 | Ticket tag cleanup | Tomás Silva | To do | 2026-11-17 |
| PRJ-110 | Escalation runbook | Ama Mensah | In progress | 2026-11-27 |
| Task ID | Task | Team | Owner | Due |
|---|---|---|---|---|
| PRJ-111 | Pricing FAQ | Docs | Lena Fischer | 2026-11-09 |
| PRJ-106 | Support macro update | Support | Ama Mensah | 2026-11-11 |
| PRJ-116 | Data export test plan | Engineering | Priya Shah | 2026-11-12 |
Change or remove shared views
- To update a view, apply it, change it, and prepare it again with the same name. The new version replaces the old one in the prepared text.
- To remove a view, clear Shared reader views, publish, then prepare again only the views you want to keep.
- Readers cannot delete shared views. Choosing one and Delete personal view is unavailable.
What to know
- Shared view settings include search and filter values and are visible to everyone who can read the page. Leave out values that should not be shared.
- A shared view is not a permission. Every reader can still see every row of the table.
- If the table’s header cells change, the section reports These views belong to a different table or header layout. Save them again for this table. Rebuild and prepare the views again.
- Conditional formatting, pinned columns and density can travel in a shared view, even though they cannot be author defaults.