Customizing CSS Safely
Overview
Customizing CSS Safely is part of the Developer Reference documentation for Rise Audit Pro. It explains how this feature works, where it appears inside the plugin, and how administrators should use it safely.
What this feature does
Customizing CSS Safely helps users review, configure, investigate, or manage the related audit and security workflow inside RISE CRM.
Why it is useful
- It helps teams understand and manage customizing CSS Safely without guessing.
- It supports safer administration, clearer accountability, and faster troubleshooting.
- It gives non-technical users a practical explanation of what the feature is for.
Who should read this?
RISE Admin, System Owner, Security Officer, Developer / Support Engineer.
Where to find it
Rise Audit Pro → Developer Reference
How to use it
- Open Rise Audit Pro → Developer Reference.
- Review the available options, filters, cards, or records related to customizing CSS Safely.
- Use the available actions only if your role has permission.
- Check related logs or reports when you need more detail.
- Document any sensitive change or investigation according to your internal process.
Example workflow
An administrator needs to review customizing CSS Safely. They open the related Rise Audit Pro page, check the visible cards, filters, or settings, then open detailed logs only when the summary indicates that deeper review is required.
Safe customization rule
Use scoped CSS and avoid overriding global RISE classes such as .card, .btn, .table, .row, .modal, or .form-control unless you intentionally want to affect the entire CRM.
Common mistakes
- Using the feature without checking the selected date range, filters, or permissions.
- Sharing sensitive audit, security, or user data with people who do not need access.
- Assuming the summary view replaces detailed investigation when a critical event is involved.
Related articles
- Activity Log Overview
- Settings Overview
- Plugin Health Overview
