Built for your question · 1 section from 1 page + 1 from the docs
Back to originalSecurity and control
Decide who can see and edit each field, by role and team.
Every change and agent action, with who did it and when.
Require a person’s sign-off before agents send or change anything you choose.
Sign in with SAML or OpenID Connect, provision users with SCIM, and require two-step login.
Choose where your customer data is stored.
Data encrypted in transit and at rest.
DocsFrom the Hourglass documentation
The site doesn't have a page for this yet, so here is the documentation, word for word.
Administration › Security
Records are encrypted at rest with AES-256 and in transit with TLS 1.2 or later. Every change to a record is kept in its history, and permissions decide who can see or edit each object and field.
Admins can add single sign-on, user provisioning, an IP allowlist and the audit log, described in the pages below.
This page has no blocks to explain.
The last 30 days of chat questions: how well the website answered them, and the gaps that keep coming back.
Open Content Intelligence ↗Pick a company, then a person, to see how each page changes for their role and industry. The companies are real; the people are fictional.
People