What Clients Can See
Overview
Client visibility should be limited to client-safe information and should never expose internal staff-only audit data.
What this feature does
It explains how Rise Audit Pro features may appear in client-facing areas, such as project history, while keeping sensitive internal logs protected.
Why it is useful
- It protects internal audit information.
- It helps administrators configure client portal features safely.
- It supports transparent project communication without exposing security data.
Who should read this?
RISE Admin, Project Manager, Client Portal Administrator.
Where to find it
RISE CRM Client Portal and project-related client-facing pages, if the feature is enabled.
How to use it
- Log in as a client test user.
- Open a client-accessible project.
- Check whether history is visible.
- Confirm only client-safe events appear.
- Adjust permissions or settings if the client sees too much information.
Example workflow
A client sees project progress history but does not see staff IP addresses, internal security notes, or system-wide audit records.
Screenshot
Screenshot required
Capture from: RISE CRM Client Portal → Project History visible to client
Capture from: RISE CRM Client Portal → Project History visible to client
Common mistakes
- Assuming staff-side and client-side history should be identical.
- Showing internal audit details to clients.
- Skipping client-role testing before publishing.
Related articles
- Client-Side Project History
- Privacy Notes for View Tracking
- Permissions Overview

