Before you start
Prepare a list of the data you plan to store, who needs access and any hosting location requirements. Do not send the data itself in a sales enquiry.
Follow these steps
- Review the workspace owner and team roles.
- List which staff need each module and which records should be restricted.
- Read the public security information and note unanswered questions.
- Contact the team about any dedicated database, hosting region, backup or contractual requirement.
- Get the proposed arrangement confirmed in writing before committing sensitive operations.
Check the result
You have a clear requirements list and a request for specific confirmation. Dedicated infrastructure is a separate arrangement to discuss with the team.
If you get stuck
If a page or older document suggests guaranteed geographic isolation or a provisioning deadline, ask for clarification. A company-scoped screen does not establish those guarantees.
One thing to remember
No dedicated infrastructure, data-residency location, certification or recovery service level is promised by this guide. Access controls still need careful configuration and verification.
Keep going
Still need a hand?
Tell us what you tried, what you expected and what happened. Keep passwords, API keys and private customer information out of your message.
Open a support ticket. Visitors without a workspace can contact us.
Still stuck?
Before contacting support:
- Confirm the workspace, record number, date range and status.
- Check your role permissions and the source document.
- Refresh once and search for the record before repeating a submission.
- Check the relevant guide for the next action; do not force a match, posting or approval.
If you still need help, include the page address, exact message, time, expected result and checks already completed. Never send passwords, API keys, payment-card details or provider secrets.