Control Who Can Create Transactions Outside Your Organization – Proof Help Center
Organizations using Proof can control whether users create transactions outside the organization's billing and management by toggling the "Allow unmanaged transaction creation" setting in Command Center's Security policies, which by default permits users to create independent transactions via their individual accounts that are not visible or billed through the organization, but when restricted, forces all new transactions to be created within the organization's managed environment accessible to team members and admins.
Audience: Organizations
How it works
Users associated with organizations can create transactions from Send & manage, and they can also upload their own documents through their individual account (accessed via their initials in the upper right corner of their Proof account).
Transactions created through a user's individual account:
- Are associated with the user's company email address.
- Are billed independently from the organization's billing setup.
- Do not require any settings configured by admin for your customer-facing transactions.
- Cannot be viewed or managed by your team members or admin.
The following settings are available in Command Center:
- Allow unmanaged transaction creation: Users in your organization can create transactions through their individual account. This is the default setting.
- Restrict unmanaged transaction creation: Users cannot create transactions through their individual accounts. Any transactions they create will appear in Send & manage and will be accessible to team members who have access to transactions.
Restricting unmanaged transaction creation does not affect permissions to send transactions from Send & manage in the organization account.
If you update this setting to restrict unmanaged transaction creation, only new transactions are affected — any transactions already pending when the setting is changed are unaffected.
Manage unmanaged transaction creation
- 1.Select Security from the navigation menu on the left.
- 2.Select Details and policies to the right of the domain you'd like to update.
- 3.Select Edit in the Independent transaction creation policies box.
- 4.Select the desired setting.
- 5.Select Save.
Summary Checklist
- This setting is in Command Center → Security → Details and policies.
- Restricting only affects new transactions — existing pending transactions are unaffected.
- Restricting this setting does not affect users' ability to send transactions from Send & manage.
Still unsure? Contact Proof Support for help.
Related
Account & Organization Administration – Proof Help Center
The Proof Help Center's Account & Organization Administration section provides detailed guidance on setting up and managing user accounts and organizations, including establishing account owners, creating title agency accounts, allowing signers without accounts, customizing branding, configuring transaction settings, controlling user access, upgrading plans, converting individual accounts to business accounts, referring friends for credits, deleting accounts, and updating notary email addresses.
Cloning a Child Organization in Command Center
The guide explains how Command Center owners and administrators can clone a child organization by copying specific settings like billing and notary instructions from an existing or root organization to create a new child organization, while noting that certain elements such as EasyLinks, API keys, and users do not transfer, and provides step-by-step instructions along with recommendations to review settings post-cloning and contact support if issues arise.
2025-06-24 Proof Release Notes
The June 24, 2025 update introduces new fraud role permissions in Defend allowing non-admin users to access fraud data, adds automatic reminder emails for real estate transactions to notify signers and contacts before expiration, and enables Command Center users to apply new brand profiles across all organizations immediately for consistent customer branding.
Company Structure: Parent and Child Organizations – Proof Help Center
The Proof company structure organizes multiple organizations into a hierarchy with root, parent, and child organizations—where parent organizations can manage settings and access data of their child organizations, users have a home organization determining their access, and certain settings like logos and configurations can be inherited from parent to child, with a maximum hierarchy depth of four levels and management facilitated via Command Center.
Edit a Business Transaction – Proof Help Center
The Proof Help Center explains that organizations can edit business transactions only while they are in Sent status—editing temporarily moves the transaction to Draft without changing recipients' existing access links, and after making changes via the Transaction actions menu and confirming with Update transaction, recipients are notified unless edits are merely saved without updating; however, these steps do not apply to real estate transactions, which require a different process.
2025-04-28 Proof Release Notes – Proof Help Center
The April 28, 2025 Proof release introduces centralized Brand profiles in Command Center, allowing customers to create and manage streamlined brand profiles across multiple organizations from a single location, now generally available to all Command Center users.