Team & Permissions

Lend1 ships with three roles: Admin, Broker and Support. Admins see and manage everything. Brokers work their own deals and clients and cannot see another broker's book. Support staff are linked to one or more brokers and see exactly what those brokers see, so an assistant working for two brokers has both pipelines and nothing else. When the defaults do not fit, build your own roles from a catalogue of more than 100 permissions grouped by feature, and assign a role to each team member when you invite them.

Built for how brokerages actually run

A two-broker firm with a shared assistant invites the assistant as Support and links them to both brokers. The assistant sees both pipelines, chases documents and books tasks on either, and never sees a deal that belongs to anyone else. When the firm hires a compliance officer, the admin creates a Compliance role with view-all access to documents and compliance settings, and nothing else. Every role change and every invite lands in the audit log.

• Deals, contacts, tasks, documents, invites and eSign requests follow the same visibility rules
• Team members can only grant permissions they hold themselves
• The Admin role is locked and nobody can promote themselves
• Per-user Connective adviser number, Google Calendar, Calendly and notification preferences
• A personal onboarding link for every broker
• AI Copilot actions respect the permissions of the person asking

Guard rails included

Permissions are enforced on the server for every screen, every report and every AI Copilot action, not just hidden in the interface. System roles cannot be deleted, a role with members cannot be removed until those members are reassigned, and only an admin can create another admin. The audit log keeps 12 months of history with field-level before-and-after values, IP address and device, filterable by action and record type.

• Starter includes 1 team member, Pro includes 5, Enterprise includes 10
• Roles managed in Settings by anyone with the Manage Roles permission
• Permanent deletion asks for confirmation and lists what goes with the user
• Audit history available on each record, not just as one long list
• Notifications route by permission, so custom roles just work