What Rise Audit Pro Does Not Track Automatically

Estimated reading: 2 minutes 6 views

Overview

Rise Audit Pro focuses on supported RISE CRM entities and plugin-aware tracking points. It does not automatically understand every custom table, third-party plugin entity, or direct database change.

What this article explains

This article explains the limits of automatic tracking and how third-party plugin tracking should be understood.

Why it is useful

  • It prevents unrealistic expectations about third-party plugins.
  • It helps administrators explain why some custom data may not appear in Activity Log.
  • It gives developers a path to integrate custom events safely.

Who should read this?

RISE Admin, Developer / Support Engineer, System Owner.

Where to find it

This applies across Activity Log, View Log, embedded history tools, and custom plugin integrations.

How to use it

  1. Check whether the action modifies a supported RISE CRM entity.
  2. Check whether the action uses standard RISE workflows or hooks.
  3. If it is a custom plugin entity, plan a custom integration or adapter.
  4. If it is a direct database update, do not assume it will be captured automatically.

Example workflow

A third-party plugin that updates a standard RISE task through the normal task model may be partially visible as a task update. A plugin that writes to its own custom table will not be understood as a meaningful entity unless it integrates with Rise Audit Pro.

Usually tracked

  • Supported core RISE entities.
  • Standard create, update, and delete flows.
  • Authentication events captured by supported filters or hooks.
  • Supported view tracking points.

Not automatically tracked

  • New custom database tables.
  • Custom plugin entities without integration.
  • Raw SQL changes that bypass RISE models or hooks.
  • External scripts modifying the database directly.

Common mistakes

  • Marketing the plugin as tracking every third-party plugin automatically.
  • Expecting custom plugin tables to appear as meaningful entities without mapping.
  • Assuming direct database changes can be audited without a tracking point.

Related articles

  • Does Rise Audit Pro Track Third-Party Plugins?
  • Supported vs Custom Entities
  • How Developers Can Log Custom Events
  • Building a Custom Integration Adapter
Share this Doc

What Rise Audit Pro Does Not Track Automatically

Or copy link

CONTENTS
Shopping Basket