Google Sheets filter views: save a personal work queue

Google Sheets filter views let you keep a focused view of shared data without making that selection everyone else’s working view. Build one named practice queue, close it, and reopen it against two expected record IDs. A filter view is not a privacy boundary and does not grant access to the spreadsheet.

Updated: 18 October 2026.

Why choose a view rather than a shared working filter?

A shared spreadsheet often serves several jobs. One person needs open tasks assigned to them; another needs completed work for a weekly review. Repeatedly changing the common working filter is not the clearest way to support both. A named filter view gives a particular selection its own reusable identity.

Google documents that different people can use different filter views at the same time. This tutorial focuses on that saved-view workflow, not on teaching every sorting option. You will create a small selection, give it a useful name, and verify that opening the name returns the intended records.

The practice data below is fictional. It is not an account of Anar's client work, and the account actions have not been run for this article. There is no measured time-saving claim. The useful output is a named view and a completed check note you can produce with harmless data in your own account.

Start on a computer with permission to edit a Google Sheets file. Google allows view-only users to create temporary filter views, but those are not saved. If you have only viewing access, distinguish that temporary exploration from the saved-view result described here rather than assuming your configuration will be available next time.

Do not confuse filtering with protection. Excluding a row from the current view does not remove the row from the spreadsheet or make it confidential. If a recipient must not see certain records, a filter-view link is not the appropriate access-control mechanism.

Prepare five records and predict the answer

In your computer browser, open sheets.google.com, confirm the intended account and choose Blank. Click the file title and name it “Filter view practice.” Select A1 and enter the table in A1:D6, including its header. One row represents one task. No customer identities, prices, or personal contact details are needed. The small list makes it possible to check every record rather than relying on whether the screen looks plausible.

Your first queue is “Alex's open tasks.” Write the expected IDs before applying any filter: J01 and J04. J02 passes the status condition but not the owner condition. J03 passes the owner condition but not the status condition. These exclusions let you check that both conditions matter.

Use consistent text in the practice cells. If the expected result is missing later, inspect the actual value rather than assuming the view is broken. A trailing space or a different spelling can make two labels that look similar behave differently. Keep the first exercise clean enough that you can explain the data without additional tools.

Record the complete starting set of five IDs as well. When you close the view, you will check that the complete practice list is visible again. This creates a clear before-and-after comparison without treating hidden rows as deleted data.

Create and name the saved view

Select A1:D6. Follow the desktop route Data, Create filter view. Open the filter icon in the Owner header. Under Filter by values, uncheck Sam, leave Alex checked and click OK. In the Status header filter, uncheck Closed, leave Open checked and click OK. Check the visible IDs against your prediction. Seeing two rows is not sufficient; the two rows must be J01 and J04.

Give the view a descriptive name such as “Alex | Open tasks | Practice.” The name describes both the responsible person and the work state. A generic name such as “Filter 1” is harder to interpret when the file eventually contains several views. Names should help someone select the right queue without trial and error.

The current Google help page describes Save View followed by Save. Complete the save controls presented in your account. Do not treat a name displayed on screen as the final persistence check. Closing and reopening the named view is a separate step and provides a clearer answer.

No sort is required for this exercise. If you add one, distinguish the selected records from their display order. The first test asks which task IDs remain, not whether they appear in a preferred sequence. Adding extra behavior before verifying selection makes a mismatch harder to explain.

If your account's interface language differs, use the control names to identify the function rather than expecting an identical screenshot. Consult the official desktop instructions linked below if your route differs. Do not switch to a normal shared filter merely because its button is easier to find; that changes the exercise.

Close, reopen, and compare IDs

Use Close at the top right of the filter-view area. Check the complete practice set again: J01 through J05. Next open Data, Change view and select the name you saved. Google notes that only one filter view can be applied at a time. Choosing another name is not a way of stacking two separate views.

Compare the reopened result with J01 and J04. If a task is missing, inspect its Owner and Status cells along with the view conditions. Renaming the view does not correct an incorrect condition. If the entire list is visible, confirm that you actually opened the saved view rather than simply returning to the sheet.

File and tab: ____
Range: A1:D6
Saved view name: ____
Owner condition: Alex
Status condition: Open
Expected IDs: J01, J04
IDs on first application: ____
IDs after closing: ____
IDs after reopening: ____
Persistence check: observed / not observed

This note separates the rule from the observed result. A screenshot can supplement it, but the note explains what the screenshot is meant to prove. Another person can compare the record IDs without guessing which part of the interface mattered during setup.

If you cannot find the saved name, do not report a successful persistence check. Revisit the save step and confirm your edit access. A temporary viewer view can be useful for exploration, but it is a different outcome from a named configuration you can reopen.

A view link and file permission are different things

With the intended view active, copy the browser URL. Google documents this as the way to share a filter-view link. If an agreed colleague already has access to the practice file, send the link with the view name and expected IDs. Keep the test within the sharing arrangement already authorized for that file.

If no colleague is available, leave the recipient check pending. You can still verify creating and reopening the view in your own account. There is no need to make the spreadsheet public or add a new external recipient just to complete this exercise.

The link does not grant spreadsheet access. File access is controlled through the sharing settings and the recipient's applicable role. When someone sees an access-request screen, diagnose a permission issue before changing the filter conditions. A valid view and an inaccessible file are not contradictory observations.

Conversely, access to the file does not prove the desired view opened correctly. Record those as two separate checks: “recipient can open file” and “recipient sees expected view.” Ask for the visible practice IDs, not merely confirmation that a browser tab opened.

Never use a view link as a substitute for separating confidential records. A person permitted to use the spreadsheet is not restricted to the rows visible in your selected view. If a business requirement is to disclose only a subset, design an appropriately limited sharing output instead of describing filtered rows as protected.

How can you keep the result maintainable?

Keep one named view and its check note. Open a new Notepad document from Windows Start, or TextEdit > File > New on Mac, using Format > Make Plain Text if needed. Copy the template, fill observed results and add the active view URL. Use Windows File > Save As or Mac File > Save to save sheets-view-check.txt in Documents; add a date if the name exists. Close and reopen that note to check its name, URL and untested steps. With accessible tools, this narrow exercise targets a fifteen-minute session, not a measured trial. Leave unobserved results pending.

• The table range includes the header and all practice records.
• The view name explains its purpose.
• Expected IDs were written before application.
• Closing and reopening were checked separately.
• File access and the recipient's view result have separate entries.

When moving to a live queue, check whether newly added records fall inside the view's range. Do not assume the fixed A1:D6 practice range is suitable for a growing task list. If an expected new task is absent, inspect the range and conditions before concluding that no work is waiting.

Keep the list of saved views understandable. If two names appear to represent the same queue, identify their owners and conditions before deciding which to retain. Removing an unnecessary view is not the same action as deleting task records. The operating note should make that distinction clear.

A short handoff can now state where to open the view, what it selects, and whom to contact if it stops matching the team's definition of open work. That is enough for the first workflow. Formula protection, change notifications, automated reminders, and AI-generated summaries are separate jobs with their own checks.

Related reading: Sheets workflow automation; Gemini in Sheets; Sheets edit notifications; File-sharing access checks; Gemini table export.