Connect an agent
Install the SDK, create a scoped key, register tools, and confirm the first policy decision.
Open quickstart →Quasentra support PRODUCT & TECHNICAL HELP
Find the answer.
Keep the boundary closed.
Start with a verified setup path, diagnose common integration problems, or send a redacted support request to the Quasentra team.
Browse by task SUPPORT PATHS
What are you trying to do?
Define permissions
Assign ALLOW, DENY, or REQUIRE_APPROVAL and keep newly discovered tools closed.
Review permissions →Resume sensitive work
Understand exact-operation approvals, expiration, argument binding, and one-time consumption.
Use approvals →Protect credentials
Move supported HTTPS, PostgreSQL, or email credentials behind the trusted gateway.
Configure gateway →Prove denial works
Use an execution witness and adversarial matrix to verify blocked tools never run.
Test the boundary →Prepare production
Check keys, versions, timeouts, failure behavior, credentials, and incident response.
Production checklist →Common diagnoses START HERE
Resolve the signal,
not bypass the control.
Do not catch a security or transport error and call the original tool. Use the reason code and request ID to identify the actual configuration or policy issue.
Agent does not appear in the dashboard+
Confirm the application ran with an API key containing agent:register, the base URL is correct, and startup did not suppress a registration error. Then review the registration checks.
A known tool is denied+
Verify the normalized action name, agent ID, active policy, API-key scope, and tenant. Unknown or mismatched tools are denied by design.
An approval cannot be resumed+
The tenant, agent, action, resource, and canonical arguments must match the original request. Expired, denied, changed, or consumed approvals fail closed.
The gateway connector fails validation+
Validation checks stored configuration and encrypted credential integrity; it does not contact the remote service. Run a non-production staging call to verify DNS, TLS, login, and firewall access.
Authorization service is unavailable+
Supported adapters fail closed after bounded retries. Preserve the request ID, inspect service health, and never run the sensitive tool as a fallback.
Before contacting support SAFE EVIDENCE
Share enough context.
Remove every secret.
INCLUDEQuasentra package versionFramework and versionRequest ID and reason codeRedacted error and relevant logsExpected vs actual result
NEVER INCLUDEAPI keys or passwordsGateway credentialsCard numbers or CVVProduction customer recordsUnredacted environment files
STILL NEED HELP?Bring the issue
Bring the issue
to our team.
Email is recommended for technical cases because it preserves request IDs, versions, and redacted evidence.
Email support →View all contact options