Skip to main content
Public table views allow you to share filtered, read-only data with residents and stakeholders through your public website. This feature helps promote transparency, inform residents about community data, and provide easy access to public information. Public table views are saved views that you can display on your public-facing website. They provide:
  • Read-only access - Residents can view and search data but cannot edit
  • Filtered data - Show only the information appropriate for public viewing
  • Custom columns - Display exactly the fields residents need to see
  • Searchable interface - Residents can filter and sort to find relevant information
  • No authentication required - Anyone can access public views
Common use cases include:

Property lookup

Let residents search for properties and view flood zone information

Permit status

Display permit applications and their approval status

Inspection results

Share completed inspection records with the community

Public records

Provide access to public documents and Elevation Certificates
Public table views are subject to visibility restrictions to protect sensitive data. Not all columns or data can be made public.

Creating a public view

To share a table view publicly, you need to create a saved view and mark it for public display.
1

Create or select a saved view

Start by creating a new saved view or opening an existing view you want to make public.Learn more about creating table views.
2

Configure appropriate columns

Add only columns that contain public information. Avoid including:
  • Internal notes or comments
  • Staff-only status fields
  • Personal contact information
  • Administrative data
  • Sensitive property details
The system will validate your columns before allowing the view to be made public. Views with restricted columns cannot be published.
3

Apply public-appropriate filters

Use filters to show only data suitable for public viewing. For example:
  • Exclude draft or pending records
  • Show only approved permits
  • Filter to completed inspections
  • Display properties in specific flood zones
4

Add a description

Write a clear description (supports markdown) explaining what the view shows. This appears above the table on the public website to provide context for residents.Good description example: “View properties in the Special Flood Hazard Area (SFHA) that have Elevation Certificates on file. Data is updated daily.”
5

Mark as public

When saving your view, check the box for “Display on public website” under visibility settings.
6

Save the view

Click “Submit” to create your public view. The system validates that your view meets public visibility requirements.
Your public table view is now available on your public website. Residents can access it through the public URL or from the website’s navigation.

Public view restrictions

To protect sensitive information, public views have specific limitations:

Restricted content

Public views cannot include:
  • Hidden or sensitive data fields
  • Columns that reference hidden tables
  • Internal workflow status fields
  • Staff notes or comments
  • Personal contact information beyond public record
  • Administrative controls or actions

Restricted table types

Some table types cannot have public views at all:
  • Tasks table - Internal workflow management only
  • Workflows table - Internal process tracking only
  • Other administrative tables

Checks

When you attempt to make a view public, Forerunner validates:
  • All columns are marked as publicly visible
  • No references to restricted tables
  • No sensitive data fields included
  • The table type supports public views
If checks fail, you’ll receive an error message indicating which columns or settings need to be changed.

How residents access public views

Public views are available to residents through several methods:

Direct URL access

Each public view has a unique URL in this format:
https://[your-community].withforerunner.com/guest/saved-views/[view-id]
You can share this link directly via:
  • Your organization’s website
  • Email communications
  • Social media
  • Printed materials

Public website navigation

Public views can appear in your public website’s navigation or as featured content, depending on your website configuration.

Search and explore

Residents can discover public views through the explore and search functionality on your public website homepage.
Work with your Forerunner administrator to feature important public views prominently on your public website.

Public view features for residents

When residents view a public table, they have access to:

View data

  • See all columns you’ve configured
  • Read-only access (no editing)
  • Formatted data exactly as you designed it

Filter and sort

  • Use column header dropdowns to sort
  • Apply filters to narrow down results
  • Search across visible fields

View details

  • Click “View” action to see detailed information
  • Navigate to related property pages
  • Access linked public documents

Mobile-friendly

  • Responsive design works on all devices
  • Touch-friendly controls
  • Optimized for mobile viewing
Residents do not need to create an account or sign in to view public table views.

Managing public views

Updating public views

You can update public views at any time:
  1. Select the public view from the views dropdown
  2. Make your changes (columns, filters, description)
  3. Click “Save” to update the view
Changes take effect immediately and are visible to all residents accessing the public URL.

Removing public access

To make a public view private again:
  1. Select the public view
  2. Click “Save” and edit visibility settings
  3. Uncheck “Display on public website”
  4. Save your changes
The view remains in your saved views list but is no longer accessible to the public.

Monitoring usage

Work with your Forerunner team to:
  • Track which public views are most popular
  • Monitor search terms residents use
  • Gather feedback on public data needs
  • Adjust views based on resident requests

Best practices

Write descriptions that explain what the data shows, when it was last updated, and how residents can use it. Use markdown formatting to make descriptions scannable with bullet points or headers.
Don’t overwhelm residents with unnecessary data. Filter views to show only information relevant to the public, such as completed inspections or approved permits.
Open your public view in an incognito/private browser window to see exactly what residents will see. Verify that all information is appropriate and understandable.
Keep public views current by reviewing and updating them periodically. Add notes to descriptions when data is updated so residents know it’s fresh.
Include a way for residents to ask questions or request corrections in your description. Link to your support email or contact form.
Share public view URLs through your organization’s communication channels. Many residents don’t know this data is available, so promote it actively.

Examples of effective public views

Example 1: SFHA property lookup

View name: “Properties in Special Flood Hazard Area” Description:
Use this tool to check if a property is located in the Special Flood Hazard Area (SFHA).

Properties shown here:
- Are located in the SFHA according to current FEMA flood maps
- May require flood insurance
- Have Elevation Certificates on file (when available)

**Last updated:** January 15, 2025

Questions? Email [floodplain@yourcity.gov](mailto:floodplain@yourcity.gov)
Columns included:
  • Address
  • Flood Zone
  • Elevation Certificate on File
  • Certificate Date
  • View Property (link)
Filters applied:
  • Flood zone is in SFHA zones (A, AE, AH, AO, V, VE)
  • Property status is Active

Example 2: Recent inspection results

View name: “Completed property inspections” Description:
View recently completed property inspections in our community.

This data includes:
- Routine compliance inspections
- Post-event damage assessments
- Follow-up inspections

Inspections are listed for the past 90 days. For older records or questions about your property, please contact our office.
Columns included:
  • Address
  • Inspection Type
  • Inspection Date
  • Result
  • Inspector Notes (public notes only)
Filters applied:
  • Status is “Completed”
  • Inspection Date is within last 90 days
  • Exclude internal or draft inspections

Example 3: Permit status lookup

View name: “Building permit applications” Description:
Search for permit applications submitted to the Building Department.

**Status meanings:**
- **Submitted** - Application received and under review
- **Approved** - Permit issued, work may proceed
- **Denied** - Application denied (contact office for details)

Data updates daily. For urgent questions, call (555) 123-4567.
Columns included:
  • Address
  • Permit Number
  • Permit Type
  • Application Date
  • Status
  • Approval Date
Filters applied:
  • Application Date within past 2 years
  • Status is not “Draft” or “Cancelled”

Troubleshooting

Solution: Your view likely includes columns or filters on restricted data. Review your columns and remove any that reference:
  • Hidden data fields
  • Internal status fields
  • Staff-only information
  • Columns from restricted tables
The error message should indicate which fields are problematic.
Solution: Check your filters. Public views may have stricter filters applied to exclude sensitive records. Review and adjust your filters to include the appropriate public data.
Solution: Verify that:
  • The view is saved with “Display on public website” checked
  • Your public website is active and configured
  • The URL you’re sharing is correct
  • Your account’s public website is published
Try accessing the view in an incognito browser window to test the public experience.
Solution: Public view descriptions support markdown formatting. Check your markdown syntax if formatting isn’t displaying correctly. Use preview tools to test your markdown before saving.

Security and privacy

Public table views are designed with security in mind:
  • No authentication bypass - Public views only show data explicitly marked as public
  • Data checks - All views are checked before being made public
  • Audit logging - Public view access is logged for security monitoring
  • Permission controls - Only users with appropriate permissions can create public views
  • No data modification - Residents can only view data, never edit or delete
Always review public views carefully before publishing. Once published, anyone with the URL can access the data. Ensure all information is appropriate for public viewing.