Skip to main content

Lifehouse CRM Dashboard & View Configuration Guide

Date: 12 May 2026
Purpose: Manual configuration instructions for Twenty CRM list views and dashboard layout

List View Column Configuration​

How to Configure Columns in Twenty CRM​

Important: The command menu (Cmd+K or clicking the search icon) is for navigation, not view customization.

To customize list view columns:

  1. Navigate to the object's list view (e.g., People, Households, Engagements)
  2. Look for the view settings icon in the list view header area:
    • This is typically a filter icon, columns icon, or view icon near the top of the table
    • It may be labeled "Fields", "Columns", or have a grid/table icon
    • Look to the right side of the search bar or above the table headers
  3. Click the icon to open the field/column selector
  4. Check/uncheck fields to show/hide columns
  5. Drag fields to reorder columns (if supported)
  6. Changes may save automatically or require clicking "Save View"

If you cannot find column customization options:

Twenty CRM may display all available fields by default, or column customization may be limited to certain views. In this case:

  • Use the table's horizontal scroll to view all columns
  • Use the built-in search and filter features to narrow down records
  • Export data to CSV for custom column selection in external tools

Troubleshooting: Finding View Customization Options​

What You're Seeing vs. What You Need​

The Command Menu (Cmd+K) - This is what appears when you:

  • Press Cmd+K (or Ctrl+K on Windows)
  • Click the search icon in the top bar
  • This menu is for navigation between objects and settings, not for customizing views

What to Look For Instead:

When you're viewing a list of records (e.g., the Locations list), look for these UI elements:

  1. Table Header Icons - Small icons above or to the right of the table columns:

    • Filter icon (funnel shape)
    • Columns/Fields icon (grid or list shape)
    • Sort icon (arrows up/down)
    • View settings icon (gear or sliders)

  2. View Name Dropdown - May show current view name with dropdown arrow

  3. Action Bar - Row of icons above the table, separate from the main navigation

If Column Customization Is Not Available:​

Twenty CRM may automatically display all fields for custom objects. In this case:

Option 1: Use Horizontal Scroll

  • The table will show all available columns
  • Scroll horizontally to see additional fields
  • This ensures all data is visible without configuration

Option 2: Use Filters to Focus Data

  • Click filter icon (if available) to narrow down records
  • Use search bar to find specific records
  • This reduces the amount of data displayed at once

Option 3: Export and Customize Externally

  • Use command menu → "Export View" or "Export Locations"
  • Open CSV in Excel/Google Sheets
  • Select only the columns you need
  • Share customized view with stakeholders

People​

Purpose: Track residents, volunteers, staff, and stakeholders

Essential Columns:

  1. Name (default) - Person's full name
  2. fieldworkRole - RESIDENT, VOLUNTEER, STAFF, TRUSTEE, COUNCILLOR
  3. consentStatus - GRANTED, NOT_ASKED, REFUSED, WITHDRAWN
  4. householdId - Link to household
  5. Emails - Contact email address
  6. Phones - Contact phone number

Optional Columns:

  • fieldworkNotes - Additional notes about the person
  • createdAt - When record was created
  • updatedAt - Last modification date

Why These Columns:

  • Quick identification of person's role in community
  • Immediate visibility of consent status for GDPR compliance
  • Contact details readily available
  • Household link shows family/address connections

Households​

Purpose: Track household units and their engagement history

Essential Columns:

  1. Name (default) - Household identifier (e.g., "Smith Household")
  2. locationId - Link to address/location
  3. contactCount - Number of times contacted
  4. lastContactAt - Date of most recent engagement
  5. notes - Household-level notes

Optional Columns:

  • createdAt - When household was added to CRM
  • fieldworkExternalId - Link to Fieldwork database

Why These Columns:

  • Shows which households have been contacted and when
  • Contact frequency visible at a glance
  • Location link provides geographic context
  • Notes field captures household-specific information

Engagements​

Purpose: Track all doorstep contacts and follow-up actions

Essential Columns:

  1. Name (default) - Auto-generated engagement title
  2. householdId - Which household was contacted
  3. personId - Who was spoken to
  4. engagementDate - When contact occurred
  5. outcome - ENGAGED, NO_ANSWER, REFUSED, etc.
  6. inputSource - TELEGRAM_VOICE, WEB_UPLOAD, etc.
  7. summary - Brief description of conversation
  8. requiresFollowUp - Yes/No flag
  9. followUpNotes - What follow-up action is needed

Optional Columns:

  • volunteerId - Who conducted the engagement
  • createdAt - When record was created

Why These Columns:

  • Complete engagement history visible in one view
  • Follow-up actions clearly flagged
  • Input source shows data collection method
  • Summary provides context without opening full record

Needs​

Purpose: Track community needs and support requests

Essential Columns:

  1. Name (default) - Auto-generated need title
  2. personId - Who has the need
  3. description - Detailed description of need
  4. confidence - CONFIRMED, INFERRED, SUSPECTED
  5. createdAt - When need was identified

Optional Columns:

  • fieldworkExternalId - Link to Fieldwork
  • sourceCreatedAt - Original capture date

Why These Columns:

  • Clear description of each need
  • Confidence level indicates data quality
  • Person link enables direct follow-up
  • Date shows when need was identified

Offers​

Purpose: Track resources and support available from residents

Essential Columns:

  1. Name (default) - Auto-generated offer title
  2. personId - Who is offering support
  3. description - What is being offered
  4. confidence - CONFIRMED, INFERRED, SUSPECTED
  5. createdAt - When offer was recorded

Optional Columns:

  • fieldworkExternalId - Link to Fieldwork

Why These Columns:

  • Quick view of available community resources
  • Person link enables matching with needs
  • Confidence level indicates reliability
  • Description provides detail for matching

Skills​

Purpose: Catalogue resident skills and capabilities

Essential Columns:

  1. Name (default) - Auto-generated skill title
  2. personId - Who has the skill
  3. description - Skill details
  4. confidence - CONFIRMED, INFERRED, SUSPECTED
  5. createdAt - When skill was recorded

Optional Columns:

  • fieldworkExternalId - Link to Fieldwork

Why These Columns:

  • Skills database for community asset mapping
  • Person link enables recruitment for activities
  • Confidence level indicates verification status
  • Description provides context for skill application

ConsentRecords​

Purpose: Track GDPR consent for data storage and contact

Essential Columns:

  1. Name (default) - Auto-generated consent record title
  2. personId - Who gave/withheld consent
  3. consentType - GDPR_GENERAL, GDPR_SENSITIVE, etc.
  4. status - GRANTED, NOT_ASKED, REFUSED, WITHDRAWN
  5. changedAt - When consent status last changed
  6. notes - Context about consent decision

Optional Columns:

  • createdAt - When record was created

Why These Columns:

  • GDPR compliance tracking
  • Clear visibility of who can be contacted
  • Date tracking for audit trail
  • Notes provide context for consent decisions

StakeholderRelationships​

Purpose: Map connections between residents and organisations

Essential Columns:

  1. Name (default) - Auto-generated relationship title
  2. personId - The individual
  3. organisationId - The organisation
  4. roleCustom - Their role (e.g., "Parish councillor", "Trustee")
  5. createdAt - When relationship was recorded

Optional Columns:

  • fieldworkExternalId - Link to Fieldwork

Why These Columns:

  • Stakeholder network mapping
  • Shows who has influence/access to organisations
  • Role clarifies nature of relationship
  • Enables strategic partnership building

Suggested Dashboard Layout​

Dashboard Overview​

Twenty CRM may not support custom dashboard widgets via API. The following layout should be configured manually through the UI if dashboard functionality is available, or replicated through saved views and reports.

Dashboard Widget 1: Households Contacted​

Type: Count metric
Data Source: Households
Metric: Total count of households with at least one engagement
Current Value: 8

Purpose: Shows reach of community engagement efforts

Dashboard Widget 2: Follow-Ups Required​

Type: Count metric with list
Data Source: Engagements
Filter: requiresFollowUp = true
Metric: Count of engagements requiring follow-up
Current Value: 4

Purpose: Action list for volunteers - shows which households need follow-up contact

Display:

  • Smith Household - Send info pack
  • Patel Household - Connect with buddy scheme
  • Brown Household - Invite to growing workshop
  • Davies Household - Connect with emergency planning

Dashboard Widget 3: Needs by Category​

Type: Bar chart or list
Data Source: Needs
Grouping: By category (if field exists) or by description pattern
Current Distribution:

  • Emergency/Health: 1
  • Education/Information: 1
  • Privacy/Data: 1
  • Community Space: 1
  • Social Connection: 1
  • Transport: 1

Purpose: Shows types of support needed in community

Dashboard Widget 4: Offers Available​

Type: Count metric with list
Data Source: Offers
Metric: Total confirmed offers
Current Value: 6

Purpose: Shows community assets available for matching with needs

Display:

  • Tools & Equipment
  • Emergency Communications (Radio)
  • Growing Skills
  • Meeting Space
  • Transport (Van)
  • Conflict Mediation

Dashboard Widget 5: Skills Available​

Type: Count metric with list
Data Source: Skills
Metric: Total confirmed skills
Current Value: 6

Purpose: Community skills database for activity planning

Display:

  • Conflict Mediation
  • Driving & Transport
  • DIY & Tool Use
  • Community Organising
  • Vegetable Growing
  • Radio Operation

Type: Pie chart or bar chart
Data Source: ConsentRecords
Grouping: By status
Current Distribution:

  • GRANTED: 5 (83%)
  • NOT_ASKED: 1 (17%)
  • REFUSED: 0 (0%)
  • WITHDRAWN: 0 (0%)

Purpose: GDPR compliance monitoring - shows who can be contacted

Dashboard Widget 7: Stakeholder Map Summary​

Type: Network diagram or list
Data Source: StakeholderRelationships
Metric: Count of relationships by organisation type
Current Value: 4 relationships

Purpose: Shows connections between residents and organisations

Display:

  • Parish Council: 1 councillor
  • Charity: 1 staff member
  • Community Group: 1 contact
  • Faith Group: 1 trustee

Dashboard Configuration Steps​

Accessing Twenty CRM Views​

Based on the command menu shown in your screenshots, Twenty CRM provides:

  • "Go to Dashboards" - Access dashboard view (if available)
  • "Create View" - Create custom saved views for objects
  • "Export View" - Export current view data to CSV

To Access Dashboard Features:​

  1. Open the command menu (Cmd+K or click search icon)
  2. Type "dashboard" or scroll to "Go to Dashboards"
  3. Press Enter to navigate to dashboard view
  4. Look for dashboard customization options in the dashboard interface itself

To Create Custom Saved Views:​

  1. Navigate to an object list (e.g., Engagements)
  2. Apply filters (e.g., requiresFollowUp = true)
  3. Open command menu (Cmd+K)
  4. Select "Create View"
  5. Name the view (e.g., "Follow-Ups Required")
  6. Save the view for quick access

If Twenty Does Not Support Dashboard Widget Customization:​

Alternative Approach: Saved Views and Reports

  1. Create Saved Views for each dashboard metric:

    • "Follow-Ups Required" - Engagements filtered by requiresFollowUp = true
    • "Needs Summary" - Needs grouped by category
    • "Offers Available" - Offers filtered by confidence = CONFIRMED
    • "Skills Database" - Skills filtered by confidence = CONFIRMED
    • "Consent Status" - ConsentRecords grouped by status

  2. Use List Views as Dashboard Sections:

    • Pin important views to navigation
    • Use view names that indicate purpose
    • Set default sort orders for priority

  3. Export Regular Reports:

    • Weekly follow-up action list
    • Monthly needs/offers matching report
    • Quarterly consent status audit
    • Annual stakeholder relationship map

  4. Create Manual Dashboard Document:

    • Maintain a separate document (e.g., Google Doc, Notion page)
    • Update weekly with key metrics
    • Include links to relevant CRM views
    • Share with stakeholders

Dashboard Widget Configuration Status​

Investigation Required: Twenty CRM dashboard widget configuration capabilities need to be verified.

Known Limitations:​

  1. No Dashboard API: Twenty CRM does not expose a REST or GraphQL API for programmatic dashboard configuration
  2. UI-Only Configuration: Dashboard setup must be done manually through the Twenty web interface
  3. View Customization: List view columns can be customized per object type
  4. Saved Views: Users can create and save filtered views for quick access

Use Twenty's built-in view customization features:

  • Configure list view columns as specified above
  • Create saved views with filters (e.g., "Follow-Ups Required")
  • Pin frequently used views to navigation
  • Use browser bookmarks for quick access to specific views

For dashboard-style overview:

  • Create a separate reporting document or spreadsheet
  • Update manually or via API export
  • Share with stakeholders as weekly/monthly report
  • Include key metrics, charts, and action items

Implementation Checklist​

Phase 1: List View Configuration (30-45 minutes)​

  • Configure People list view columns
  • Configure Households list view columns
  • Configure Engagements list view columns
  • Configure Needs list view columns
  • Configure Offers list view columns
  • Configure Skills list view columns
  • Configure ConsentRecords list view columns
  • Configure StakeholderRelationships list view columns

Phase 2: Saved Views Creation (15-20 minutes)​

  • Create "Follow-Ups Required" view (Engagements)
  • Create "Consent Granted" view (People)
  • Create "Confirmed Offers" view (Offers)
  • Create "Confirmed Skills" view (Skills)
  • Create "Active Needs" view (Needs)

Phase 3: Dashboard Alternative (if needed)​

  • Investigate Twenty dashboard widget capabilities
  • If no dashboard: Create external reporting document
  • Set up weekly metric collection process
  • Share dashboard/report with stakeholders

Training Notes for Staff​

Using List Views Effectively:​

  1. Sorting: Click column headers to sort by that field
  2. Filtering: Use filter icon to narrow down records
  3. Searching: Use search bar to find specific records
  4. Bulk Actions: Select multiple records for bulk updates
  5. Export: Export filtered views to CSV for external analysis

Best Practices:​

  • Update follow-up status after completing actions
  • Add notes to engagement records for context
  • Check consent status before contacting residents
  • Use saved views for common tasks (e.g., daily follow-up list)
  • Review dashboard metrics weekly to track progress

Summary​

List view configuration: Manual UI configuration required for 8 object types
Dashboard widgets: Twenty CRM does not support programmatic dashboard configuration
Recommended approach: Use saved views + external reporting document
Implementation time: 45-60 minutes for full setup

Dashboarding should be handled through saved views and external reports until Twenty CRM adds native dashboard widget functionality.