Enroll an existing submitted application in a brokerage workspace
Add an application that already exists and is already submitted to an existing named brokerage workspace; this flow enrolls a file and does not create a borrower application.
Before you start
- Be signed in to MLO Operations with an active named membership in the target workspace.
- Have an existing submitted borrower Application ID and the two-letter jurisdiction for the file.
- Be an active workspace owner or supervisor who currently owns the application through its broker profile; the API does not permit arbitrary applications to be enrolled.
Step by step
Open the existing workspace
Open Brokerage Operations from the Brokerage section. If more than one workspace is available, select the intended name in the workspace selector at the top. Do not use Initialize Brokerage Desk or Create Workspace for this enrollment.
Open the Files tab
Choose Files and locate the Active Files panel. Select Enroll File, which opens the Enroll Application dialog.
Confirm the enrollment scope
Read the dialog text: it enrolls an already-submitted application that you currently own, and does not create a new application. Confirm you are using the intended workspace and application before entering data.
Enter the existing application details
Enter the numeric Application ID and the two-letter Jurisdiction, then select Execute Enrollment. The form defaults Jurisdiction to CA but accepts another two-letter state code when appropriate.
Open the enrolled file
After success, the Active Files table shows File Ref, App ID, Jurisdiction, Revision, and Open. Confirm the App ID and jurisdiction, then choose Open to work in the scoped file record.
Check your work
- The file appears in Active Files with a File Ref, the existing App ID, jurisdiction, and a revision such as v1.
- Opening the row shows the existing borrower application and the brokerage file record rather than a newly created borrower application.
- The enrollment is recorded in the brokerage audit trail.
Troubleshooting
The API says only a submitted borrower application can be enrolled.
Return the application to the borrower portal and confirm it has completed Submit My Loan Package. Draft or merely analyzed applications are not eligible for brokerage enrollment.
The API says you do not currently own the application through its broker profile.
Confirm that the application came through the broker profile associated with the signed-in actor. Do not guess an Application ID or copy an application from another broker.
Enrollment is forbidden even though the application exists.
Ask a workspace owner to confirm your active named workspace role. The enrollment endpoint requires an active owner or supervisor and a workspace membership; a global platform-admin flag alone is not a substitute for the named workspace role.
The API says the application is already enrolled.
Use Active Files and search the App ID already listed in the workspace. Do not submit the same application again; open the existing File Ref instead.
Important limits
- Workspace roles are scoped to a brokerage workspace and differ from global platform roles. Access in one workspace does not imply access in another.
- Use only the generic help path here; never publish a real workspace ID, file ID, application ID, Clerk ID, token, or private file URL.
- Once enrolled, borrower legacy edits are controlled by the named brokerage workspace as stated in the dialog. Coordinate changes through the workspace workflow rather than asking the borrower to create a duplicate application.
- Enrollment is an operational record, not a licensing determination. Company and individual authority still need to be recorded before regulated assignments or stage actions.