> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/run-your-studio/working-with-lists.md).

# Working with lists

Filters, columns, saved views and search. How to make Schedulink show you the work that matters to you.

Accounts, Events, Tasks, Contacts and Employees all open as lists, and every one of them can be shaped to show you what you care about. Two people at the same studio can look at the same page and see something quite different, because these settings are personal to each user. Changing yours doesn't change anyone else's.

## Filtering

The filter bar runs down the left of every list. Use it to narrow what you're looking at: today's jobs, unstaffed events, your own open tasks, accounts in one district.

Filters persist. Set one and it's still there when you come back tomorrow, which is convenient once you know it and confusing when you don't.

When you type into a filter, all the words have to match. Searching a filter for "Montessori Day School" returns accounts with all three words, not everything containing "day" or "school".

{% hint style="info" %}
If a record you're certain exists isn't in the list, clear your filters before assuming anything is wrong. A filter set weeks ago and forgotten is the most common reason something appears to have vanished.
{% endhint %}

### Saving a filter

Once you've built a combination you use often, save it. It then sits in the filter bar ready to apply in one click, which is worth doing for the two or three views you open every day.

Saved filters belong to you, not to your studio, so building a good set for yourself doesn't affect your colleagues. You can delete them when they stop being useful.

### Seeing archived records

Archived records drop out of the normal list so your team sees live work. They're not gone. Use the archived toggle on the filter bar to bring them back into view, on any list.

That's how you find last season's events, an account you stopped working with, or a photographer who worked for you two summers ago.

## How many records you're looking at

Under every list is a count, reading something like 21 to 40 of 360. The first pair is the page you're on, the last number is everything that matched.

It respects your filters, so it doubles as a check on whether a filter did what you meant. Filtering events to a district and seeing 4 of 4 when you expected forty tells you something is wrong with the filter, not with your data.

## Choosing your columns

Click the **three dots** at the top right of any list and choose **Set Columns**. Tick the fields you want to see and untick the ones you don't, then drag the column headers to reorder them.

This includes your custom fields, so anything your studio tracks can become a column. A coordinator might want expected head count and setup time visible on the events list, while an editor cares about none of that.

Like filters, columns are personal to you.

## Exporting a list

**Export** sits in the same three dots, and gives you an Excel file. You'll be asked which kind.

**Simple** is one sheet with the standard fields, which is what you want for a quick list of names and dates.

**Grouped** gives each template its own worksheet, with that template's custom fields alongside the standard ones. Templates don't share custom fields, which is why those can't all sit on one sheet.

Either one respects the filters you've applied, so filter first and export second. The record count tells you how many rows you're about to pull, and times and dates follow your studio's timezone.

## The three dots menu

Alongside Set Columns and Export, the same menu holds **Import** for bringing data in from a sheet.

## Views on the Events list

Events can be shown three ways, not just as a list.

**List** is the default table. **Calendar** lays your jobs out by date, which is the fastest way to spot a week that's overbooked. **Map** plots them by location, which is useful when you're routing photographers across a region and want to see which jobs are near each other.

## Global search

The search bar at the top of the screen looks across everything, not just the page you're on. Results come back grouped into tabs for Accounts, Events, Tasks, Contacts and Employees, so click the tab for the kind of thing you're after.

All the words you type have to match, so a two-word name finds records containing both.

Archived records are left out. If you're looking for last season's event or a photographer who's moved on, use the archived toggle on the filter bar instead.

Use search rather than filtering when you know the name of what you want. Filtering is for browsing a set of records; search is for finding one.

## Downloading a single record

Export gives you a list. For one record, open it and choose **Generate PDF** from the three dots inside the record.

That works on accounts, events and tasks. An event PDF is the job sheet your photographers carry; account and task PDFs carry their details, contacts and custom fields.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://schedulink.io/help-center/run-your-studio/working-with-lists.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
