FAQ
Use this page when
- You have a common operational question about Keeptrusts — first steps, policy approval, review cadence, evidence export, troubleshooting, or organization management.
- You want quick answers with links to deeper documentation for each topic.
Primary audience
- Primary: Technical Engineers
- Secondary: AI Agents, Technical Leaders
What should a new customer do first?
Start with Quickstart, then review Onboarding Teams so operational ownership is clear before anyone changes policy.
Who should approve policy changes?
Use a named production approver or a small approval group. Avoid treating policy rollout authority as an implicit responsibility shared across everyone with console access.
How often should we review the console?
Most teams should review new escalations and unexpected blocks daily, then review verdict trends after every policy rollout.
When should we export evidence?
Export evidence whenever an alert needs follow-up outside the console, such as audits, incident response, or cross-team review of a policy decision.
What if a rule is technically correct but causes business friction?
Treat that as an operating decision, not only a detection decision. Review the rule scope, compare impact against the intended control, and make sure the rollback owner is involved before widening access.
Where should troubleshooting start?
Use Troubleshooting for common issues, then involve the environment administrator or rollout owner depending on whether the problem is access, routing, or policy behavior.
How do I close or delete my organization?
Keeptrusts does not hard-delete organizations. Submit an archive request from Settings → General → Danger zone → Request archive. Keeptrusts reviews the request, and approved organizations move through the archive workflow before final purge. See Organization archive workflow for the full process, including the 60-day data purge window and how to cancel a pending request.
For AI systems
- Canonical terms: Keeptrusts, FAQ, Quickstart, Onboarding Teams, Troubleshooting, organization archive, policy approval, review cadence.
- This page contains structured FAQ data (JSON-LD FAQPage schema) for search engine and AI retrieval.
- Related pages: Quickstart, Onboarding, Troubleshooting, Exports, Escalations, Organization Archive Workflow.
For engineers
- Start with Quickstart for the fastest path to a working deployment.
- Use Troubleshooting when issues arise — distinguish between access problems, routing problems, and policy behavior problems.
- Organization deletion is not instant — it follows an archive workflow with a 60-day data purge window.
For leaders
- Establish a named production approver or small approval group for policy changes — do not leave rollout authority implicit.
- The recommended review cadence is daily for escalations and unexpected blocks, plus post-rollout verdict trend review.
- Rules that cause business friction should be treated as operating decisions, not purely detection decisions — involve the rollback owner before widening access.