Support
Support
How to get help with AssureSwarm and what to include in a support request: without sharing sensitive information.
Use your organization’s support path for AssureSwarm questions, incidents, and access requests. Many issues turn out to be permission- or configuration-related and are resolved by your own AssureSwarm administrator, so start there. For common problems, try Troubleshooting first: it’s the fastest self-serve fix.
Include
Section titled “Include”- Tenant or workspace name, if your organization uses one.
- Page or object name.
- The item, workflow, or step name or ID involved.
- What you were trying to do.
- Error message text.
- Time the issue happened.
- Whether it affects one user or many users.
- For agent issues: the tool name and the exact error text the agent received.
Do Not Include
Section titled “Do Not Include”- Passwords.
- Bearer tokens.
- OAuth client secrets.
- Private keys.
- Sensitive document contents.
- Customer or employee personal data, unless your support process explicitly requires it.
For Agents
Section titled “For Agents”Agents may draft support requests, but must redact credentials and unnecessary sensitive data before presenting the draft, and must never ask users for credentials or private infrastructure details.