Two-factor authentication (2FA)
Quill supports two-factor authentication using email verification codes, alongside trusted-device management and additional verification for sensitive actions.
Quill brings access management, controlled sharing and publishing oversight into the way your team works with data. Manage how insights are accessed, reviewed and shared, with security features built into your workflow.
Access control, sharing controls and logging built into the workflow.
Decide who can see and change what, from whole accounts down to a single report.
Quill supports two-factor authentication using email verification codes, alongside trusted-device management and additional verification for sensitive actions.
Administrator, uploader, reader and guest roles support different levels of responsibility. Manage permissions across accounts, workspaces, folders and reports to reflect how your team works.
Workspace membership and permissions underpin Quill’s database access policies, providing a structure for managing access across teams and projects.
Grant or deny access to individual reports and folders. Tailor access to specific pieces of work alongside your broader workspace permissions.
Available as an option, single sign-on lets your people sign in to Quill with their existing work account through your company’s identity provider — Microsoft Entra ID, Okta, Google Workspace or any SAML 2.0 provider. Joiners, movers and leavers follow the process you already run.
Reach the right audience with the version you meant to publish.
Report sharing is governed by role-based access controls by default. When you need to reach a wider audience, reports can also be shared publicly with password protection. Signed access tokens support verified access and can be invalidated when needed.
Track report revisions and select the version you publish. Quill’s publishing workflow gives teams a way to review changes before releasing an updated report to its audience.
Quill uses sandboxed frames for interactive report rendering, restricting how embedded content interacts with the main application.
Agents and automated workflows work inside the same permissions as your people.
MCP access is available only to validated Quill accounts and uses the same role-based permissions as the platform. These permissions govern which content connected AI agents can access and which actions they can perform.
Logging captures key agent interactions with Quill, showing which agents are working on behalf of which users and what actions they take. This gives your team visibility into automated activity and a record to support review and investigation.
Connect tools and automated workflows using API keys with read and write permissions. Keys are stored as hashes and can be revoked when access is no longer needed.
Customer review sessions give support staff temporary, account-scoped access, providing a defined window for investigation and assistance.
A record of what happened, and a check before sensitive content travels further.
Logs capture authentication events, administrative changes, publishing activity and API usage, helping teams investigate activity and understand how Quill is being used.
Quill screens report samples for potentially sensitive information and flags findings for administrator review, supporting your team’s checks before sharing content more widely.
Set up your workspaces, roles and sharing rules the way your team already works, then publish with oversight built in.