Permissions for a real estate inquiry integration

The decision to make first

A pilot may need only limited lead creation while a connection request offers broad access to contacts, transactions, documents and administrative settings. Define the exact objects and actions required, then have the account owner approve the narrowest practical permissions for that workflow.

What the handoff should contain

Record account identity, allowed fields, permitted actions, prohibited records, credential owner and the process for removing access after the pilot.

Suggested wording to approve

Example wording: “This connection is for the agreed inquiry handoff. It should not expose private transaction documents or change unrelated client records.”

Test the difficult case

Test the permitted inquiry action and a deliberately prohibited action in an approved test environment, then inspect the permission failure. Do not place administrative keys in public website code, demo profiles, screenshots or assistant prompts that may be visible to visitors.

Worked example

Fictional example: The pilot only needs to create an inquiry, yet the proposed credential can also read transaction documents. The account owner should review a narrower permission approach before activation. In testing, the allowed inquiry action should succeed while an unrelated document-read action remains unavailable; a broad administrator key is not evidence of a well-scoped connection.

Review it in operation

Review access when staff, vendors or scope change and remove connections that no longer have an active operational owner.

Check before you launch

• Define the exact objects and actions required, then have the account owner approve the narrowest practical permissions for that workflow.
• Record account identity, allowed fields, permitted actions, prohibited records, credential owner and the process for removing access after the pilot.
• Test the permitted inquiry action and a deliberately prohibited action in an approved test environment, then inspect the permission failure.
• Review access when staff, vendors or scope change and remove connections that no longer have an active operational owner.

Related guides