Recommended Settings for Production

Overview

Recommended Settings for Production is part of the Settings 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

Recommended Settings for Production 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 recommended Settings for Production 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 → Settings

How to use it

1. Open Rise Audit Pro → Settings.
2. Review the available options, filters, cards, or records related to recommended Settings for Production.
3. Use the available actions only if your role has permission.
4. Check related logs or reports when you need more detail.
5. Document any sensitive change or investigation according to your internal process.

Example workflow

An administrator needs to review recommended Settings for Production. 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.

Recommended baseline

• Enable logging for critical entities.
• Restrict export and purge permissions.
• Use retention settings that match your internal policy.
• Exclude sensitive fields that should not be stored in logs.
• Review Plugin Health after configuration changes.

Screenshot

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