What it covers
Use the Settings trust controls for a governed request workflow, with the request state kept separate from ordinary CRM customer records.
Intelligence and security
Privacy and support requests
Submit and follow account-related support, privacy and security requests.
How it works
Keep an account request on a clear path
Privacy and support controls give a signed-in account a defined way to raise requests about its NovaSoft service. Settings brings the relevant trust and request entry points together, so a person can explain the issue and review the recorded request state. These requests concern the account or service relationship with NovaSoft; they are separate from the Service Desk tickets a business handles for its own customers. The distinction helps the user choose the right route when asking about support, privacy, security, export or deletion.
In practice
A request has a governed lifecycle and requester-visible state. Sensitive completion work uses separate operator authority and review; creating a request does not automatically execute a deletion, change another person’s access or complete a data export.
When to use it
Useful situations
- Raise an account-support question through the relevant Settings controls.
- Ask about privacy, security or deletion with a clear written request.
- Review the recorded state of an existing request before submitting another one.
A working path
How the work moves
Choose the correct request
Open the trust or privacy area in Settings and choose the supported request type. Describe the account or service issue clearly, including the outcome you need. Use your own customer Service Desk for business-customer cases instead.
Explain the relevant context
Provide the requested details without placing passwords, access keys or recovery codes in the message. Check the subject and description before submitting so the reviewer has enough information to understand the request and its intended scope.
Track the recorded outcome
Return to the request list to inspect its status and recorded outcome, or use the supported close control for an eligible request. For privacy or deletion work, wait for the governed review and confirmed completion instead of treating submission as proof that the requested action ran.
Illustrative scenario
An account privacy question
A workspace owner submits a privacy request about the supported export of their business records. They follow the recorded request state and completion outcome, while the ordinary CRM remains the place for their own customer work.
Before you start
What to check
- Do not include live credentials or recovery codes in a request. The reviewer can ask for the appropriate non-secret evidence through the governed process.
- A deletion or privacy request needs review and current authority; submission is not an immediate destructive action or a promised legal outcome.
Is this my customer service queue?
No. These requests concern the NovaSoft account or service. Use Service Desk to manage requests from your business’s customers.
Does a deletion request remove data immediately?
No. It enters the supported review workflow. Completion has separate authority and is reported through the request state.
Get started
See your customer work in one place.
Start with the core CRM for free, then add the tools your team needs.