Book a DemoSecurity and responsible access
Protect the brokerage file while giving each participant the access their work requires.
Broker Pilot is a hosted, multi-tenant brokerage application with authenticated access, multi-factor authentication, role-aware permissions, and deal-specific transaction coordinator assignments. Client portals separate client-facing activity from internal brokerage work, and optional Google connections require the account holder's authorization.
Account and identity controls
Broker Pilot accounts use authenticated sign-in and multi-factor authentication. A user can choose to remember an approved device for a limited period, while unfamiliar or expired devices require verification again.
Brokerage, role, and deal access
Brokerage membership and user roles determine the broad areas a person can access. Deal assignment further limits which transaction an agent or transaction coordinator works on. An assigned coordinator gains access to that deal and its related client transaction rather than every file by default.
Document and signing controls
Documents can be classified for view-only use, prepared for signing, or recorded as already signed. Signature-field ownership helps prevent recipients or unrelated participants from accidentally deleting fields prepared by another person.
Client portal separation
Buyer and seller portals expose only the client-facing documents, forms, net sheets, signature requests, and status selected for that client. Internal compliance notes, brokerage configuration, and commission operations remain within authenticated team workflows.
Shared responsibility
Security also depends on how each brokerage configures users, shares documents, maintains Google connections, and removes access when responsibilities change. Broker Pilot is an operational tool and does not replace a brokerage's legal, regulatory, privacy, retention, or cybersecurity obligations.
Frequently asked questions
Answers about security and responsible access
Does Broker Pilot support multi-factor authentication?
Yes. Broker Pilot can require a verification code after password authentication and can remember an approved device for a limited period.
Can clients see internal brokerage information?
Client portals are separate from the internal brokerage workspace and display only client-facing information made available through the workflow.
Does a transaction coordinator see every deal?
No. The transaction coordinator workflow is based on assignment to an individual deal unless the user separately holds another role with broader access.
Can Google integrations be disconnected?
Yes. Users can disconnect Google Calendar and Google Drive from Broker Pilot settings.