Who Should Use Rise Audit Pro?
Overview
Rise Audit Pro is useful for several roles inside a company or agency using RISE CRM. Each role uses the plugin differently depending on what they need to monitor, review, or investigate.
What this article explains
This article explains the main user types for the plugin and what each one should focus on.
Why it is useful
- It helps you decide who should have access to each part of the plugin.
- It reduces security risk by encouraging role-based access.
- It makes the documentation easier to follow because not every reader needs the same level of detail.
Who should read this?
System Owner, RISE Admin, Staff User, Client Portal User, Developer / Support Engineer.
Where to find it
Access depends on the permissions configured in RISE CRM roles and plugin settings.
How to use it
- Identify who needs to view audit logs.
- Identify who needs to manage settings, exports, API keys, and compliance tools.
- Assign permissions based on responsibility.
- Review permissions regularly.
Example workflow
A finance manager may need access to Finance Audit Trail and invoice changes, while a support agent may only need limited Activity Log access for tickets and projects.
Main roles
System Owner
Uses executive reports, dashboards, security summaries, and finance audit trails to understand operational risk and team accountability.
RISE Admin
Manages plugin settings, permissions, retention, API keys, alert rules, exports, and troubleshooting.
Staff User
May use project history, task audit panels, watchlist features, or limited activity logs depending on permissions.
Client Portal User
May see limited project history or client-side activity if those features are enabled and allowed.
Developer / Support Engineer
Uses technical reference articles, API documentation, hooks, routes, database tables, and integration information.
Common mistakes
- Giving client portal users access to internal audit data.
- Giving every staff member export or purge permissions.
- Not separating admin documentation from developer documentation.
Related articles
- Permissions Overview
- Recommended Settings for Production
- What Staff Can See
- What Clients Can See
