Workspace and access settings can affect other users immediately. Work in the intended workspace, grant the smallest necessary access, and review the impact before saving.
The names of buttons and sections can vary with your PloverCRM plan, permissions, connected services, and current version. When a label differs, use the matching label displayed in your account and do not change an unrelated setting.
Safe troubleshooting order. Confirm the correct account, workspace, connected website, browser, and user role. Record the exact non-sensitive error, affected screen, approximate time, and last successful step. Check the relevant status page or log before changing configuration. Make one low-risk correction at a time and wait for the result. Verify the result before retrying or escalating. Do not delete records, reinstall plugins, reconnect integrations, or rerun imports merely because a page looks stale; these actions can change data or create duplicates.
- Open the team, workspace, settings, or permissions area named in this guide.
- Confirm the workspace name, connected website, and your administrator access.
- Review the current user, role, scope, connection, or saved workspace before making a change.
- Choose the specific add, edit, invite, switch, or access action.
- Enter only verified details and select the narrowest role, scope, or setting that meets the requirement.
- Review affected teammates, records, connections, and pending invitations.
- Save or confirm the change and wait for PloverCRM to report success.
What to verify #
After the final step, confirm:
- The workspace name and connected website still match the intended destination.
- The status, record, filter, setting, or result reflects the change you made.
- No unrelated lead, teammate, connection, message, or automation was changed.
- Any export, notification, file, or external action follows your organization’s privacy and retention policy.
PloverCRM should display a confirmation, updated status, or refreshed record. If the workflow is asynchronous, use its progress or log view instead of submitting the same request again.
Troubleshooting #
- If the screen or control is missing, confirm the workspace and ask an administrator to review your role.
- If results are empty or stale, clear filters, refresh once, and check workspace connection status.
- If a value is rejected, read the field-level message and use the required format.
- If an operation is processing, wait for its status or log entry before trying again.
- If the result is unexpected, stop before making another change and record the exact non-sensitive message, approximate time, browser, and reproduction steps.
