Managing views

Views in Dalil AI 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 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 Kanban board, or collapsible groups in a table)

Example: You could create a view showing "People located in Dubai with a Dalil Score above 70", displaying only the fields Name, Job Title, Company, and Dalil Score, sorted by highest score first.

Where to Find Views

Every entity in Dalil starts with a default All view. The All view is always available; it cannot be deleted, and it acts as the default view whenever you open an entity.

To switch views or create a new one, click the current view name (for example All) in the top-left area of the entity screen, just below the entity name. This opens the view picker, where you can select an existing view or click Add view to create a new one.

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

• People
• Companies
• Opportunities
• Tasks
• Notes
• AI Meeting Notes
• Analytics

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

Dalil provides two view layouts: Table and Kanban (also called a Board).

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 Dalil Score.

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 → Closed Won / Closed Lost.

When you create a Kanban view, Dalil asks which Select field to group by. If the entity has no Select field yet, you'll need to add one first; the view picker will prompt you with "Set up a Select field to create a Kanban".

You can create both Table and Kanban views on the same entity and switch between them at any time from the view picker.

Filters and Sorting

Views become powerful when combined with filters and sorting.

Filters

Click Add filter in the view bar to display only records that match specific conditions. Filters support a wide range of conditions depending on the field type:

• Text: is, contains, doesn't contain, is empty
• Numbers: greater than, less than
• Dates: is before, is after, is relative (e.g. "last 30 days"), is in the past, is today
• Select fields: is, is not
• Relations: is a specific record (e.g. Company is "Acme Inc")

Examples:

• City = Paris
• Contact Type = Prospect
• Opportunity Stage = Proposal
• Created in the last 30 days

For more complex logic, use Advanced filter to combine multiple conditions with AND / OR groups. For example: (Stage is Proposal OR Stage is Negotiation) AND Amount greater than 10,000.

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

Sorting controls the order in which records appear. Examples:

• Sort by Dalil Score descending to prioritize the hottest 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

Changes you make to a view (filters, sorts, visible fields) can be saved so the view always opens configured the same way. All saved views are listed in the view picker dropdown, and everyone in the workspace can use them.

From the view picker you can:

• Rename a view (Edit) to make it easier to understand
• Delete a view you no longer need (except the default All view)
• Add a view to Favorites to access it directly from the sidebar

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 Dalil Score

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

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 Dalil's AI analyze records more effectively and provide context-aware signals and recommendations.

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.