Activate Full Compliance Applications
Run the module installer through normal module activation and verify that its menu and records are available.
Exact navigationAdmin Area → Setup → Modules
Before you begin
- Confirm the module is active and use the exact navigation shown above.
- Use an account with the stated module and core CRM permissions.
- Use known test records when changing statuses, visibility, saved filters or global navigation.
What this guide covers
Run the module installer through normal module activation and verify that its menu and records are available. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open Admin Area → Setup → Modules.
- Locate the record, setting or action used to activate full compliance applications.
- Complete the displayed fields or controls exactly as described in this guide.
- Select the available save, submit, update, call, sign, upload or confirm action.
- Return to the related register, portal, dashboard or call panel and verify the recorded result.
Fields, choices and supported possibilities
WorkspaceAdmin Area → Setup → Modules
ActionRun the module installer through normal module activation and verify that its menu and records are available.
Code-backed validations and workflow rules
- The action is available only when the supplied module exposes it and the signed-in user has the required module and core CRM access.
- Hidden helpers and internal background methods are documented under the user-facing workflow they support rather than presented as separate menu pages.
Expected result and verification
- The activate full compliance applications workflow completes without a validation, permission or availability error.
- The relevant case, document, proposal, call, extension, widget session, timeline or audit evidence shows the expected state.
- Any client-visible or public result appears only where the code explicitly allows it.
Security, privacy and operational checks
- Use a controlled test case, contact, extension or website origin before production rollout.
- Grant the minimum permissions needed and protect private documents, call metadata, signing evidence, API credentials and infrastructure paths.