Managing views

Views in Vetta define how your CRM data is displayed and organized. They allow you to create different perspectives on the same records without changing the underlying data.

Each entity (such as People, Companies, or Opportunities) and each pipeline can have multiple views. This allows teams to quickly access the exact information they need without manually reapplying filters or settings.

What a view is

A view is a saved configuration that defines how records appear in your workspace. Each view combines several elements:

• Layout: Table or Board (Kanban)
• Visible fields: Which fields are shown, in what order, and which stay hidden
• Filters: Conditions used to include or exclude records
• Sorting: The order in which records are displayed
• Grouping: How records are grouped (the columns of a board, or collapsible groups in a table)

Example: You could create a view showing "People located in Dubai who are Decision makers", displaying only the fields Name, Job Title, Company, and Last interaction, sorted by most recent interaction first.

Where to find views

Your views sit as tabs above the list, starting with All. The All view is the entity's default list: it is always there and cannot be deleted. When an entity has more views than fit in the row, the rest are in a menu at the end of the row, where Search views helps you find one.

Click a tab to switch views. Each tab has its own menu with the options described in Saving and organizing views.

Views are available on every entity in your workspace, including:

• People
• Leads
• Companies
• Opportunities
• Tasks
• Custom entities

Pipelines also support multiple views, allowing you to analyze the same pipeline using different perspectives, such as a Kanban board by stage or a table sorted by revenue.

Table view vs Kanban view

Vetta provides two view layouts: Table and Board, also called Kanban.

Table view

Table view displays records in rows and columns, similar to a spreadsheet. This layout is ideal when you want to see many details at once.

Example: A People view showing Name, Company, Job Title, Last Contacted, and Persona.

Table view is typically used for analysis, filtering, and data management. Tables can also group records. For example, grouping Opportunities by Stage shows each stage as a collapsible section.

Kanban view

Kanban view displays records as cards arranged in columns, grouped by a Select field, usually a stage field. This layout is useful for visualizing progress in a process: drag a card to another column to update the record.

Example: An Opportunities board showing deals moving through stages such as Discovery, Proposal, Negotiation, then Closed Won or Closed Lost.

When you create a board, Vetta asks which Select field to group by. If the entity has no Select field yet, you'll need to add one first; Vetta prompts you to set up a Select field to create a Kanban. See Managing fields.

You can create both Table and Board views on the same entity and switch between them at any time.

Filters and sorting

Views become powerful when combined with filters and sorting.

Filters

Click Filter in the view bar to display only records that match specific conditions. The first rule starts with Where: pick a field, a condition and a value, for example Account Status is Active outreach. The count at the bottom of the list updates as you go.

Narrated video · 1:04

Narrowing a long list with filters. On People, click Filter and add rules such as Account Status is Active outreach and Job Title contains CEO, watching the count change. Between rules choose And (both must match) or Or (either is enough); all rules at one level share the choice, so mix them with Add rule group, for example Job Title contains CEO Or Founder inside a group. Use it to find a slice of contacts. Sorting and saving the result is a separate video.

Transcript

Your People list has thousands of contacts, and you only need a slice of them. Click Filter. The first rule starts with Where: Account Status is Active outreach. Watch the count at the bottom of the list: it drops from over nine thousand to just over five thousand. Now add a second rule: Job Title contains CEO. Between the rules you choose And or Or. And means a contact must match both, so the count drops to about seventeen hundred. Switch to Or, and matching either one is enough, so it grows to over six thousand. All rules at the same level share that choice, so to mix them, use a rule group. Set it back to And, remove the job title rule, and click Add filter rule, then Add rule group. Inside the group: Job Title contains CEO, Or Job Title contains Founder. Now the list shows people in active outreach who are a CEO or a founder, about twenty-nine hundred of them.

Filters support a wide range of conditions depending on the field type:

• Text: Contains, Doesn't contain, Is empty, Is not empty
• Numbers: Greater than, Less than
• Dates: Is before, Is after, Is relative (e.g. "last 30 days"), Is in past, Is today
• Select fields: Is, Is not
• Relations: Is a specific record (e.g. Company Is "Acme Inc")

When you add a second rule, choose And or Or between them:

• And means a record must match every rule, so the list gets shorter
• Or means matching any one rule is enough, so the list grows

All rules at the same level share that choice. To mix them, click Add filter rule, then Add rule group, and build the group inside. For example: Account Status is Active outreach And a group of Job Title contains CEO Or Job Title contains Founder shows people in active outreach who are a CEO or a founder.

Filters on relation fields match specific linked records. To slice records by an attribute of a related record (for example, People at Healthcare companies), add that information as a field on the record itself; enrichment and workflows can fill it automatically.

Sorting

Click Sort and pick a field, and the list lines up in that order. Click the arrow on the sort chip to flip it, and the cross to remove it. You can stack sorts, and they apply in order: sort by Job Title, then add Name, and people with the same title line up by name.

Examples:

• Sort by Estimated MRR descending to prioritize the biggest opportunities
• Sort by Last Contacted date to identify contacts that need follow-up

Sorting ensures the most important records appear first.

Saving and organizing views

Once a filter and sort are in place, click Save as new view, give it a name, and pick Table or Board (a board groups records into columns by a Select field, such as Persona). Your new view sits as a tab next to All, and opening it brings back its filters, sorts and visible fields. Everyone in the workspace can use saved views.

Narrated video · 1:06

1 linked topic

Sorting a list and saving it as a view. Click Sort, pick a field such as Name, flip A to Z with the arrow chip, remove it with the cross, or stack sorts that apply in order. Then Save as new view, name it, and choose Table or Board, which groups records into columns by a field like Persona. The view becomes a tab next to All and the button reads Update view when you change it. The tab menu has Set as default, Add to Favorite, Edit, Duplicate view and Delete.

Transcript

You've built the perfect filter, and you don't want to rebuild it tomorrow. First, put it in order. Click Sort and pick Name, and the list lines up from A to Z. Click the arrow on the sort chip to flip it, Z to A, and the cross removes it. You can also stack sorts, and they apply in order. Sort by Job Title, then add Name: the titles line up first, and people with the same title line up by name. Now save it. Click Save as new view and give it a name, like CEOs and founders. Pick Table, or Board, which groups people into columns by a field like Persona. Keep Table, and save. Your new view sits as a tab next to All. Open it, and the filter and both sorts come back with it. Change anything here, and the button now says Update view, so one click keeps the change. Hover the tab and open its menu. Set as default moves it to the front, and Add to Favorite pins it in your sidebar. Edit renames it, Duplicate view makes a copy, and Delete removes it again.

Change anything on a saved view, and the button reads Update view, so one click keeps the change.

Hover a view's tab and open its menu to:

• Set as default: moves the view to the front, so the entity opens on it
• Add to Favorite: pins the view in your sidebar
• Edit: renames the view
• Duplicate view: makes a copy you can change without touching the original
• Delete: removes the view (the All view cannot be deleted)

Favorited views appear in the sidebar nested under their parent entity or pipeline, and can be organized into favorite folders. For example, if you favorite a view called "Enterprise Prospects" on the Companies entity, it will appear under Companies in the sidebar.

Examples of views in action

People

• CEOs in Europe, sorted by last interaction

Companies

• Prospects displayed in Kanban grouped by customer journey stage

Opportunities

• Deals created in the last 30 days, displayed in Table view sorted by Owner

Customer success teams may also use multiple pipeline views:

• Onboarding view: Shows companies in early stages with fields such as Kick-off Date, CSM, and Next Task
• Steady-state view: Displays active customers with renewal dates and expansion potential

To take a view's records out of Vetta, export it to CSV; see Managing records in table view.

Why views matter

Save time: Filters and settings are saved, so teams do not need to reconfigure data each time.

Stay organized: Different workflows such as sales, fundraising, or customer success can each have dedicated views.

Collaborate better: Views are shared across the workspace, so teams can favorite the same views and align around the same data.

Enable AI insights: Clear views help Vetta's AI analyze records more effectively and provide context-aware signals and recommendations.

Common questions

Key outcome

Views allow you to organize and explore your CRM data from different perspectives. By using views effectively, your team can quickly switch between prospecting, pipeline management, and customer success workflows while always working with the same structured data.