Purpose
Multi-Stakeholder Collaboration lets lenders invite any stakeholder on a deal into Built, not just a single borrower contact. Sponsors, guarantors, general contractors, capital partners, and diligence service vendors can all be granted platform access to a deal, each at an access level the lender controls.
Previously, only one borrower stakeholder and one diligence service vendor could collaborate on a deal in Built. Every other stakeholder existed as a record only. This release opens deal collaboration to the full set of parties who actually work a deal, and gives lenders the tools to manage that access over the life of the deal.
Key Features
Feature 1: Fewer prerequisites to send an invitation. A deal no longer needs a Project, locked Sources and Uses, or a Draw Workflow before you can invite someone to collaborate. You can send the invitation as soon as you know who belongs on the deal.
Feature 2: Multiple collaborators per deal. Each deal supports several active collaborators at the same time, each with their own invitation and access level. Only one collaborator per deal can hold Full Access.
Feature 3: Access for non-borrower stakeholder types. Sponsors, guarantors, general contractors, capital partners, and other stakeholder types can now receive platform access, not just a record on the deal.
Feature 4: A single Stakeholders list. The Stakeholders page shows every stakeholder in one flat list instead of splitting them into separate Internal and External sections. Adding a stakeholder follows the same flow regardless of type.
Feature 5: Ongoing access management. Change a collaborator's access level, remove their access, or resend an invitation at any time from the deal's Collaborator Access tab.
Feature 6: Primary Collaborator column on the Portfolio grid. The Portfolio grid includes a Primary Collaborator column showing who holds Full Access on each deal, and stays current as collaborator access changes.
Feature 7: Diligence Service vendor onboarding. Diligence Service vendors can be invited into Built through a standardized onboarding flow, with the vendor admin role assigned automatically on first signup.
Feature 8: Clearer contact and organization management. Organization creation follows one consistent flow across CLA+, individual contacts can be archived, and "Archived" replaces "Inactive" as the label for organizations and contacts that are no longer in use.
Target Users
Lender users who manage deals and decide who needs access to them — relationship managers, draw administrators, and deal teams.
Deal stakeholders who receive an invitation — borrowers, sponsors, guarantors, general contractors, and capital partners.
Diligence Service vendors who need Vendor Portal access to view and fulfill diligence service orders.
How It Works
Stakeholders and collaborators are separate
A stakeholder is a record. It captures who has a relationship to a deal — a sponsor, a general contractor, a guarantor — and lives on the deal's Stakeholders page. A collaborator is someone who has been granted access to that deal in Built.
Creating a stakeholder record does not give anyone access to Built. Granting access is a separate, optional step, so you can keep a complete record of the parties on a deal without inviting all of them into the platform.
Viewing stakeholders on a deal
Navigate to Portfolio > Deals > [Deal Name] > Stakeholders. All stakeholders appear in one list with three columns:
Stakeholder Type — the party's role on the deal (General Contractor, Borrower, Draw Administrator, Vendor, Relationship Manager, and so on)
Organization — the company the stakeholder belongs to
Deal Contact — the named individual and their email address
Select + Add Stakeholder to add a new stakeholder to the deal. To invite stakeholders to collaborate in Built, use the Manage Access link in the banner at the top of the page.
Figure 1 — The Stakeholders page shows every stakeholder on the deal in a single list.
Access levels
Four access levels control what a collaborator can do on a deal:
Access Level | What the collaborator can do | Limits |
|---|---|---|
Full Access | Submit draws, upload documents, and manage deal data. | One collaborator per deal. |
Vendor Access | Review and fulfill order requests for the deal. | Assigned to diligence service vendors. |
Limited Access | View draws and deal data, and view and upload documents. | Cannot submit draws or change deal data. |
Read-only Access | View draws, deal data, and documents. | Cannot upload documents, submit draws, or make changes. |
Inviting a collaborator and managing access
Go to Portfolio > Deals > [Deal Name] > Settings > Collaborator Access. The Manage Deal Collaborator Access panel lists every stakeholder on the deal alongside their current invitation status.
Figure 2 — Manage Deal Collaborator Access lists each stakeholder, their access level, and the available actions.
From this panel:
Invite — send an invitation to a stakeholder showing as Not Invited.
Change — update the access level of a stakeholder who has already been invited.
Re-send — refresh and resend an invitation showing as Invite Pending. Use this when a collaborator never accepted the original invitation.
Removing access entirely is also handled from this panel.
Selecting Invite opens the Invite Deal Collaborator panel, where you choose the access level and select Send invitation.
Figure 3 — The Invite Deal Collaborator panel, where you select the access level before sending.
What the collaborator sees
Once a collaborator accepts their invitation and signs in, their access level for the deal appears in the page header next to the capital provider, labeled My Deal Access. This gives collaborators a clear view of what they can do on the deal without having to ask.
Figure 4 — A collaborator sees their access level in the deal header as My Deal Access.
Finding the primary collaborator on the Portfolio grid
The Portfolio grid includes a Primary Collaborator column showing the individual who holds Full Access on each deal. It updates as collaborator access changes, so it always reflects current access.
Primary Collaborator is distinct from the Borrower column. The borrower on a deal is not always the person granted Full Access, so the two columns can show different people.
Diligence Service vendor onboarding
Diligence Service vendors are invited into Built through the same global onboarding flow used for other stakeholders, by way of an invite-contact workflow. When a vendor signs up for the first time, the vendor admin role is assigned automatically, so no separate role setup is needed.
The onboarding experience shows the vendor which lender and which deal the invitation came from, so vendors working with several lenders know exactly which relationship they are accepting. Vendors use this access to view and fulfill diligence service orders in the Vendor Portal.
Organizations, contacts, and archiving
Adding an organization follows one consistent Add new Organization flow across CLA+.
Archived replaces Inactive as the label for organizations and contacts that are no longer in use.
Individual contacts can be archived, not just organizations.
Archiving preserves the record and its history. Existing organization and contact data is unchanged by this release.
Benefits
Invite collaborators as soon as you know who belongs on a deal, without first setting up a project, locking sources and uses, or building a draw workflow.
Bring every party who works a deal into Built — sponsors, guarantors, general contractors, and capital partners — rather than routing everything through a single borrower contact.
Give each collaborator only the access their role requires, using four distinct access levels.
Adjust access as a deal evolves: change a level, remove access, or resend an invitation without involving support.
Find every stakeholder on a deal in one list, without navigating between internal and external sections.
Identify at a glance which collaborator holds Full Access on each deal from the Portfolio grid.
Onboard diligence service vendors through a standardized flow, with the right role assigned automatically.
Best Practices
Reserve Full Access for the party who submits draws. Only one collaborator per deal can hold Full Access, so assign it to the party responsible for submitting draws and managing deal data. There is no cap on Limited or Read-only collaborators.
Create the stakeholder record first, decide on access second. Keeping a complete stakeholder list is useful on its own. Invite only the stakeholders who need to work in Built.
Match the access level to the work. Read-only Access suits parties who only need visibility. Limited Access suits parties who contribute documents but should not submit draws.
Resend before troubleshooting. If a collaborator never accepted their invitation, use Re-send to refresh the invite link. If they have trouble with onboarding itself, contact Built support.
Archive instead of deleting. Archiving an organization or contact keeps the record and its history intact while removing it from active use.
Read the Primary Collaborator column carefully. It shows who holds Full Access, which is not necessarily the borrower on the deal.
FAQ
Can I invite someone who isn't a borrower?
Yes. You can invite any stakeholder type — sponsors, guarantors, general contractors, capital partners — to collaborate on a deal in Built. You assign their access level when you send the invitation.
How many collaborators can I have on one deal?
Multiple. Each person receives their own invitation and access level independently of others on the same deal. The only limit is that one organization or individual per deal can hold Full Access. There is no cap on Limited or Read-only collaborators.
What can collaborators see or do?
It depends on the access level you assign. Full Access gives the broadest visibility, including submitting draws and managing deal data. Limited Access allows viewing draws and deal data and viewing and uploading documents, but not submitting draws or changing deal data. Read-only Access allows viewing draws, deal data, and documents only. Vendor Access allows a diligence service vendor to review and fulfill order requests for the deal.
What if I invited the wrong person, or someone needs a different access level?
You can change a collaborator's access level or remove their access at any time. Go to Settings > Collaborator Access on the deal to make the change.
The collaborator never accepted the invitation. What should I do?
Select Re-send on Settings > Collaborator Access. The invitation link refreshes. If the collaborator is having trouble with the onboarding flow itself, contact Built support.
What's changing for our diligence service vendors?
Diligence Service vendors can now be invited into Built through a standardized onboarding flow. They receive an invitation showing which lender and deal they are being connected to, and are assigned the vendor admin role automatically on first signup. Vendors use this access to view and fulfill diligence service orders in the Vendor Portal.
Will my existing stakeholder data change?
Your existing records are intact. The visible differences are the flattened stakeholder list that replaces the internal and external section split, and "Archived" in place of "Inactive." No data was deleted or restructured in a way that affects existing workflows.
What's the difference between a stakeholder and a collaborator?
A stakeholder is a record — it captures who has a relationship to a deal, such as a sponsor, general contractor, or guarantor. A collaborator is someone who has been granted access to that deal in Built. You can have a stakeholder record without giving that person access to Built. Granting access is a separate, optional step.