Security Policies
Set org-wide defaults and override per-team — re-auth windows, idle timeouts, session limits, and MFA requirements. Stricter for production, relaxed for dev.
What You Get
Org-Wide Defaults, Team-Level Overrides
Force re-authentication after configurable hours (org-wide or per-team)
Idle timeout auto-logout after inactivity (org-wide or per-team)
Limit concurrent sessions per user to prevent credential sharing
Enforce MFA for all organisation members with a single toggle
Team-level overrides — stricter policies for sensitive departments
Teams inherit org defaults unless explicitly overridden
Real-time enforcement — policy changes apply to active sessions
Full audit trail for every policy change with admin attribution
API-driven configuration for infrastructure-as-code workflows
Available on Business and Enterprise plans
Policy Engine
Security Policy Configuration
Deploy in Under 5 Minutes
Three Steps to Secure Access
1. Sign Up With SSO
Connect your identity provider — Okta, Azure AD, Google Workspace, or any SAML/OIDC provider. Your team logs in with existing credentials.
2. Add Your Resources
Register servers, databases, Kubernetes clusters, and web apps. Define who can access what with role-based policies.
3. Access Securely
Your team accesses resources through the browser — identity-verified, session-recorded, and audit-logged. No VPN, no exposed ports.
Try Security Policies — Free for 14 Days
From signup to your first secure session in under 5 minutes. No infrastructure changes, no credit card, no sales call.