When to use Traceless
Use Traceless if your end users have mixed MFA tools. It routes each push to the user’s existing factor, so you don’t need to connect Duo and Microsoft 365 separately for verification. If all your clients use the same provider, for example Microsoft 365 everywhere, you can use that provider’s native push instead. See Identity verification.How to connect
You need API credentials from your Traceless admin settings.1
Get your Traceless credentials
Sign in to Traceless as an organization admin. From the admin settings page, copy your API signing secret and Organization UUID.
2
Connect Traceless
In Rallied, go to Settings → Integrations, find the Traceless card and click Connect. A credentials form appears.
3
Enter your credentials
The push method applies to every verification Traceless handles for your MSP. To change it later, reconnect Traceless with the new value.
4
Save and confirm
Click Save. Rallied validates the credentials against the Traceless API. The card shows Connected when complete.
How verification works
When the agent decides an action is sensitive, such as a password reset or an admin permission change, it asks Traceless to verify the requesting employee.1
Agent requests verification
The agent asks Traceless to challenge the employee using their work email. Traceless finds the right device in your connected MFA system.
2
Employee receives a push
The employee gets a push notification on the configured authenticator app and approves it from their phone.
3
Rallied polls for the result
Rallied polls Traceless every few seconds until the verification resolves or the window closes.
4
Agent proceeds or stops
On approval, the agent continues the plan. On denial, timeout, or failure, the agent stops and tells the requester.
Turn off requester verification
Traceless verifies requesters before the agent acts on sensitive tickets. It can also deliver credentials to employees through one-time secret links. You can turn off verification and keep Traceless for secret links only.If One-Time Secret is also connected, the agent uses One-Time Secret links by default. It uses Traceless when the requester or dispatcher asks for Traceless or SMS delivery, or when a workflow or your Custom Instructions say to.
Secret-link delivery through Traceless still works when verification is off.
Outcome notes on tickets
When verification starts from a PSA ticket, such as a new ConnectWise service ticket flagged as sensitive, Rallied posts an internal note on the ticket as soon as the verification resolves.Limits and timing
- The verification window is 5 minutes from the moment Traceless sends the push. After that, the verification expires and the agent doesn’t execute the action.
- While a verification is pending, the agent’s tool execution pauses for the entire client session. No further actions run until the verification resolves.
- Every new sensitive request needs a fresh verification, even from the same employee.