Skip to content
DoorEngine

Security & data

Every connection starts with your permission.

Before we connect anything, we agree on which accounts are involved, what information is needed, and which actions are allowed.

Example scope

DoorEngine wants to connect to your CRM

For one workflow: Intake to assigned work

Allowed
  • View client contacts
  • Add notes and file links
  • Update the deal stage
Not included
  • Delete records
  • Export your database
  • Other agents' clients
You can revoke this connection at any time.

The right customer account

A connection works only within the access the customer grants and the provider supports. Working with several agents never implies access to all of their records.

Only the work you authorize

Records, actions, and permissions are scoped to the specific workflow. Where a provider offers narrower permissions, we use them.

Clear handling of information

Before an integration goes live, we document the information it processes, where it goes, what is retained, and how retention and deletion work.

A way to disconnect

Every implementation explains how to revoke the provider connection and what happens to any retained information afterward.

These principles guide the service we're building. Implementation details are agreed for each deployment. This website doesn't connect to your CRM or transaction accounts, and the inquiry form only prepares an email draft. Please don't include API keys, client documents, or sensitive transaction details in a first message.

Have security requirements? Bring them early.

Tell us about your organization's access and data requirements as part of the workflow conversation.