Page Views vs Modal Views

Estimated reading: 5 minutes 5 views

Rise Audit Pro tracks record access in two different ways: Page Views and Modal Views.
This helps administrators understand who opened a record, whether it was viewed from a full page or from a popup/modal inside RISE CRM.

This is important because many RISE CRM workflows do not always open records as full pages. Tasks, projects, invoices, estimates, proposals, clients, leads, tickets, expenses, contracts, and orders may be opened from quick-view popups or AJAX modals.

What is a Page View?

A Page View is recorded when a user opens a full RISE CRM page for a supported entity.

Examples:

  • Opening a project page.
  • Opening a task page directly.
  • Opening an invoice page.
  • Opening an estimate, proposal, ticket, client, lead, expense, contract, or order page.

Page Views are useful when administrators need to know who accessed a full record page and when that access happened.

What is a Modal View?

A Modal View is recorded when a user opens an important entity detail popup or AJAX modal inside RISE CRM.

For example, when a user opens a task from the task list and RISE CRM displays the task details inside a popup, Rise Audit Pro records that access as a Modal View.

Modal Views help capture real user behavior that would otherwise be missed if the audit system only tracked full page loads.

Why Modal View tracking matters

RISE CRM relies heavily on modals and quick-view screens. Without Modal View tracking, a user could open and inspect a record without triggering a traditional page view.

By tracking Modal Views, Rise Audit Pro gives administrators a more accurate access history.

  • See who opened a task from a popup.
  • Confirm whether a staff member inspected a record without editing it.
  • Track access to important entity details opened through AJAX views.
  • Differentiate between full page access and quick modal access.
  • Improve audit coverage across common RISE CRM workflows.

Supported Modal View examples

Rise Audit Pro can track important entity detail modals, including supported AJAX view screens for:

  • Tasks
  • Projects
  • Invoices
  • Estimates
  • Proposals
  • Clients
  • Leads
  • Tickets
  • Expenses
  • Contracts
  • Orders
Note: Available modal tracking depends on how the installed RISE CRM version opens each entity. Some modules may open as full pages, while others may use AJAX modals.

What is not tracked as a Modal View?

Rise Audit Pro does not track every popup or interface element. This avoids unnecessary noise in the audit log.

The following UI-only interactions are not treated as Modal Views:

  • Confirmation dialogs.
  • Dropdown menus.
  • Date pickers.
  • Tooltips.
  • Small settings popups.
  • Non-entity interface dialogs.

Only meaningful entity detail views are recorded.

How View Source appears in View Log

The View Log includes a View Source column. This column shows whether the record was opened as a full page or inside a modal.

  • Page View: The user opened a full entity page.
  • Modal View: The user opened an entity detail popup or AJAX modal.

This makes it easier to answer questions such as:

  • Did the user open the full record page?
  • Was the record viewed from a quick popup?
  • Who inspected this record without making changes?
  • Which records are frequently viewed from modal workflows?

Using the View Source filter

If the View Source filter is available, administrators can filter the View Log by:

  • All view sources
  • Page View
  • Modal View

This helps teams separate full page access from quick-view popup access during investigations.

Duplicate prevention

Rise Audit Pro includes duplicate prevention for repeated views within a short time window.

For example, if the same user opens the same task modal multiple times within a short period, Rise Audit Pro avoids creating excessive duplicate records.

Page Views and Modal Views are handled separately. A full page view does not suppress a later modal view, and a modal view does not suppress a full page view.

Privacy and compliance notes

View tracking records access metadata such as the viewed entity, viewer, IP address, device, view source, and timestamp.
It does not modify the original record.

Administrators should make sure View Log access is limited to trusted roles, such as administrators, audit viewers, security managers, or compliance officers.

Suggested screenshots

Add a screenshot of the View Log table showing both Page View and Modal View records.

screenshots/view-log-page-vs-modal-views.png

If the View Source filter is enabled, add a second screenshot showing the filter dropdown.

screenshots/view-log-source-filter.png

Troubleshooting

Modal views are not appearing in View Log

Confirm that the entity is opened through a supported detail modal or AJAX view. Some modules may open as full pages depending on the RISE CRM version or theme customization.

The same modal does not create a new row every time

This is expected. Rise Audit Pro prevents duplicate view records within a short time window to avoid noisy logs.

Older records do not show a clear View Source

Older View Log records created before Modal View tracking may appear as Page View or Unknown Source depending on the available metadata.

The Country column shows Unknown country

This means the IP address was captured but could not be resolved to a country. The raw IP address remains available for audit review.

Add a Comment

Your email address will not be published. Required fields are marked *

Share this Doc

Page Views vs Modal Views

Or copy link

CONTENTS
Shopping Basket