Frontline has two working layouts. A list is a table: rows, columns, and a familiar scan from top to bottom. It is the right home for People, Companies, and any record type you mostly search, sort, and update in bulk. A kanban is a board. Records sit on cards, grouped into columns by a select field, usually Stage on Deals or Status on Tickets. You drag a card to move the work.

Deals open as a pipeline for a reason. Tickets open as a board for the same reason. You can still add a list on those objects when you need a forecast grid or a filtered export. You can add a kanban on People if you ever group by a select, but most wealth teams keep contacts in a list and keep the board for mandates and service work.

When you create a view you pick the layout, give it a name, and choose sharing. Shared means the rest of the workspace can open it. Private means it is yours. A private view is a good place for “my book” or a messy filter you are still testing. A shared view is what the team should land on, like Pipeline or All contacts.

A view is more than a layout. You can filter it. The filter builder starts with “Where,” then a field, then a condition. You can add another condition, or a group of conditions, when the rule is more than one line. Advisors might save a list of Contacts where review cadence is this month and IPS on file is no. Operations might save Tickets where status is On You. Clear the filters when you want the full set again. Apply them when the view should remember the rule.

You also choose which fields show. The toolbar will tell you something like “12 of 15 fields.” Hide what the board or list does not need. On a pipeline card you might keep value, company, owner, and last interaction. On a contact list you might keep name, email, household, and review cadence. The fields still exist on the record. The view is only choosing what to put in front of you.

Sorting belongs on lists especially. Sort Contacts by review cadence, or by last interaction, so the quiet households rise. Kanban is already ordered by the column you grouped on. You can still decide what appears on the card.

Both list and kanban can carry calculations. A calculation is a total on a column for the rows in that view, after filters. Sum of mandate value on Pipeline. Average AUM on a household list. A count of filled review dates. On a kanban, the same idea can sit on a column, so Closed Won shows the dollars in that stage, not only the cards. Deals ship with a sum on Value for this reason. Add the calculation to the view you actually use, not to every view by habit.

Every record type can have a default view. That is the shared landing spot when someone opens Leads, Contacts, or Deals. It has to be a shared list or kanban, not a private view, and not a record layout. Set Pipeline as the default on Deals if that is how the firm runs. Set a contact list as the default on Contact. New hires should not have to hunt for the board.

You can also pick a default for yourself. In the view menu, star the view you want to open next time. That star is yours. It does not change the record type’s default for everyone else. Joaquin can star Joaquin’s Deals. You can star Pipeline. The yellow star is the one Frontline will bring you back to on that object.

Use that split on purpose. The record type default is the team’s front door. Your star is how you sit down in the morning. If a private view is your star, that is fine. Do not make a private view the team default. Frontline will not let that through, and it would hide the front door from everyone else.

On Deals, keep a shared Pipeline grouped by stage, with value summed on the board. Add a shared list called Book if you need a spreadsheet of every open mandate. Advisors can add private views for their own names, or star the shared Pipeline if that is enough.

On People, Lead can default to a list sorted by next step. Contact can default to a list filtered to upcoming reviews. Someone in operations might star a private view of Contacts missing an IPS. James still appears in all of them. The view is the lens, not a second database.

Create views from the menu with New view. Name them the way people will say them out loud. “Pipeline.” “My book.” “Reviews this month.” If you need a new object or a new record type to make a view work, you went too far. Change the filter first.

Next we will invite the people who will live in these views, and the roles that decide what they can change.