Block Unmanaged Account Creation with Command Center – Proof Help Center
Organizations using Proof can prevent unauthorized account creation with their email domain by enabling the "Block unmanaged account creation" feature in Command Center—after verifying their domain and enabling Command Center, admins can restrict all users from creating unmanaged accounts via sign-up, invitations, or document signing by navigating to Security settings and activating this policy.
Audience: Organizations
Prevent unauthorized users from creating an account associated with your organization by blocking unmanaged accounts. Once restricted, users cannot create an account with your email domain without an invitation from your organization.
Even if you don't use domain-based single sign-on (SSO), you can restrict unmanaged accounts to prevent unauthorized transactions from your company's email domain. Once enabled by an owner or admin, all users in your organization are affected.
Prerequisites
Your account must meet both of the following requirements to restrict unmanaged accounts:
- 1.Your account has Command Center enabled.
- 2.Your domain has been verified.
What to expect after restricting unmanaged accounts
Once unmanaged accounts are restricted, any attempts to create an account on Proof by a user with an email address associated with your domain will be blocked. This includes when:
- A user tries to sign up on the website
- Another account tries to invite a new user
- Someone tries to create an account to sign a document
Restrict unmanaged accounts
- 1.Select Security from the menu on the left.
- 2.Select Details and policies for the domain you'd like to restrict.
- 3.Select Edit.
- 4.Select Password-based authentication.
- 5.Select Block unmanaged account creation.
- 6.Select Save.
Summary Checklist
- Prerequisites: Command Center enabled and domain verified.
- Navigate to Security → Details and policies → Edit → Password-based authentication → Block unmanaged account creation → Save.
- Once restricted, all three account creation paths (sign-up, invitation, document signing) are blocked for your domain.
If you are still unsure, contact Proof Support for help.
Related
Why RON is Critical to Stopping Deed Fraud
The article explains that rising deed fraud in the U.S. threatens homeowners' valuable assets, and highlights how remote online notarization (RON) combats this by employing rigorous multi-step digital identity verification—including knowledge-based authentication, extensive credential analysis with over 25 checks, and manual notary review—thereby creating a more trustworthy record than traditional in-person notarizations and helping to prevent fraudulent property transfers.
Proof vs. The Competition: A Smarter, Safer eSign Alternative
Proof Sign distinguishes itself from typical eSign platforms by integrating identity-first security measures like government ID scans and biometric verification directly into a unified, scalable workflow that supports both standard and notarized signatures, offers proactive fraud detection through real-time behavioral monitoring, and enables rapid, branded deployment via EasyLinks—resulting in up to 40% cost savings and 50% faster closing times for enterprises.
Proof Trust Center Security
Proof Trust Center Security ensures robust protection of customer data through AES 256-bit encryption, TLS 2.1 communication, enterprise key management, sophisticated access controls including SCIM and SSO, centralized management via Command Center for large organizations, and a comprehensive security program featuring 24/7 incident response, penetration testing, and continuous monitoring.
Multi-Factor Authentication (MFA) Overview
Proof employs multi-factor authentication (MFA) to enhance security by requiring users to provide two or more verification factors—knowledge, possession, or inherence—where login MFA, mandatory for all notary accounts, protects account access via codes sent by text or authenticator apps, while transaction MFA, available only to organizations, verifies recipient identity through phone authentication with premium tiers allowing voice call options for sign-only transactions.
Domain-Based Single Sign-On (SSO) Overview – Proof Help Center
Domain-Based Single Sign-On (SSO) for Proof allows organizations to enable secure, centralized authentication through their existing identity providers (like Okta, Microsoft Azure, or Google IDP), requiring users to log in via the organization's domain-verified IDP, disabling separate Proof passwords and usernames, and ensuring all users with the organization's email domain are provisioned and authenticated through the IDP, while owners and admins retain password access and users outside the controlled domain are recommended to use MFA.
Tackling Healthcare Fraud With Medical Licensing
Healthcare fraud, a costly industry-wide crisis driven by identity impersonation of doctors, patients, and insurers, can be effectively countered by strengthening identity verification during medical licensing through automated biometric and ID scanning technologies that provide licensing boards with verifiable digital identity reports and fraud-risk scoring.