Views

A view is a saved way of looking at your records. "Owners in Logan Square with more than twenty units." "Everything I toured in March." "The forty buildings on the Q3 target list."

It holds three things, and they used to be three separate features:

• What is in it — a filter, records you added by hand, or both.
• How it looks — which columns, in what order, how wide, pinned columns, and any colour rules.
• Who it is for — yours, or shared with everyone in your organisation.

Views live in the Database workspace. The Filter button in the top bar names the view you are in and how many conditions it has, and opens the view drawer — a Filters tab and a Columns tab over the same view.

Two ways to decide what is in a view

A filter

Open Filters and Add condition: Units is greater than or equal to 20. Conditions are AND-ed together.

You can filter on any column, including custom fields you created and formula columns you wrote. That is the part worth knowing — the old filter panel offered about a dozen fixed controls, so the fields that mattered most to your business were the ones you could not filter by.

A filtered view is live. Buy a building that matches and it appears, without you touching the view.

One condition is not a column at all: Shared with asks who can see the record itself, not who the view is shared with — Anything I can see, Only me, Me and specific people, A team, or Everyone at the organisation.

Records you pick

Select rows and choose Add to view, or use Add to view in a record's action menu. This is what research lists used to be, and every list you had is now a view holding the same records.

A view built this way is a fixed set. Nothing joins it until you put it there.

Both together

If a view has records pinned to it, the filter narrows those records rather than searching everything. Pin forty buildings, then filter to the ones over twenty units, and you get a subset of your forty — not forty plus everything else over twenty units.

One set of records, three ways to look at it

Every view is read through Properties, People or Companies, and the tabs switch between them without changing what is in the view.

Ownership carries membership across. A view holding forty properties, read through People, gives you the people who own them — which is the list to call. Read the same view through Companies and you get the LLCs. Add a person to a view and the Properties tab shows what they own.

Group by

On the Filters tab, properties can be grouped None, Owner or Company — each owner or company shown once, with its properties nested under it. It is a display shape rather than part of the saved view, so it stays put as you switch between views.

Columns

The Columns tab shows what is on the table, in order. Tick a field to show or hide it, drag it to reorder, and pin one to keep it visible while the rest of the table scrolls. The list leads with a curated set; Show all fields reveals everything else, including the fields nobody has asked for yet — a search for a field's name always searches all of them, curated or not.

Any column can carry conditional formatting: numbered rules, first match wins — red if overdue, amber if due soon. Add as many as a column needs and reorder them, since the order is what makes two rules that could both match behave predictably.

If the column you want does not exist yet, New formula column opens the formula editor without leaving the drawer.

Sharing

A view is yours until you share it. A shared view is visible to everyone in your organisation and anyone can edit it, which is the point — "the Q3 target list" should be one thing, not one per person.

Your column layout is not shared. Everre keeps a personal default view per entity that saves your columns as you drag them, and that one stays yours.

Saving changes

Changing filters or columns on a named view marks it as changed rather than saving straight away — a saved question should not quietly become a different question. The drawer's footer offers Save as new view always, to branch off without touching the one you are in, and Save to name once a named view is open and has unsaved changes. The unnamed default view keeps autosaving on its own, so there is nothing of its own for that second button to commit.

Have your agent do it

Your agent can see your views and run them:

Pull the Q3 targets view and draft an intro email to each owner.

Make me a view of every multifamily building over 30 units with no activity in six months.

Who owns the buildings in the Logan Square view?

Running a view gives the agent the same records you see, with your filter and your pinned records applied — so you do not have to describe what you meant.