Set up workspace staff, cases, and company readiness
Manage named workspace membership, log operational cases, and maintain the company authority fields required for jurisdiction-aware assignments.
Before you start
- Open an existing Brokerage Desk workspace with an active named membership.
- For staff changes, be a workspace owner. For case work, use an allowed named workspace role and an active case owner. Company Authority edits are owner-only.
- Use approved, already-provisioned identities and accountable licensing evidence; this guide does not create credentials or bypass identity checks.
Step by step
Review the workspace scope
Open Brokerage Operations and select the workspace name from the top selector. Remember that the selected workspace, not a global admin screen, scopes the Staff, Cases, Company, and Files data.
Add or update named staff
Open Staff and select Add Staff. In Provision Staff, enter Display Name and the existing person's System ID (Clerk ID or Email), choose Assigned Role (Owner, Supervisor, Processor, Compliance, or MLO), and select Add Member.
Record regulated staff evidence
For an MLO or supervisor who may receive regulated work, enter Licensed States, Individual License Number, Sponsorship Reference, License Evidence Reference, and License Expiry. Use Edit and Save for an existing row, or Revoke / Restore to change active membership.
Maintain company authority
Open Company. In Company Authority, maintain Company NMLS Number, Licensed States (Comma separated), License Expiration Date, and License Evidence URL / Reference, then select Save Credentials. Non-owners see Read-only mode.
Log a case
Open Cases and choose Open Case. In Initialize Case, choose Classification (Compliance, Complaint, or Records), enter Summary, optionally enter External Reference (Optional) and Due Date (Optional), choose an active Case Owner, and select Log Case.
Resolve and audit the case
In Cases & Audits, use Edit / Resolve for an open row. Choose a status such as Open, In progress, or Closed, keep an active owner, enter Resolution details when closing, and select Save Case. Reopen / edit is available for a closed row.
Confirm readiness before assignment
Use Company Authority values and the individual member evidence together with the file jurisdiction. The backend requires current company state authority and current eligible individual licensing before a regulated MLO or supervisor assignment.
Check your work
- Staff & Roles lists the named member, role, active state, system identity, and recorded states.
- Company Authority saves the company NMLS, licensed states, evidence reference, and unexpired date for the workspace.
- Cases & Audits lists the case with a classification, status, summary, and owner, and closed cases include a resolution.
- An eligible assignment can pass the workspace and member authority checks for the file jurisdiction.
Troubleshooting
The company form is read-only.
Only a named workspace owner can modify Company Authority. Ask an existing owner to update the fields; do not attempt to use a global admin role as a substitute.
A regulated assignment is rejected for authority or licensing.
Check that the workspace has the file jurisdiction in Licensed States, Company NMLS Number, License Evidence URL / Reference, and a future License Expiration Date. Check the assignee's active role, matching licensed state, license number, sponsorship reference, license evidence, and expiry.
Add Member cannot find or verify the identity.
Use the person's exact approved Clerk ID or exact Clerk email for the already-provisioned account. The server verifies the identity; this flow does not create an account or accept a guessed identifier.
A case cannot be closed.
Enter Resolution details before selecting Closed. The API rejects a closed case without a resolution and requires an active workspace member as Case Owner.
A case description is rejected as restricted.
Do not put SAR-specific content in this Cases & Audits workspace. The API explicitly keeps SAR-specific content in the approved restricted system.
Important limits
- A named workspace role (Owner, Supervisor, Processor, Compliance, or MLO) is not the same as a global platform role (Admin, Company admin, MLO, or Pending). Never infer one from the other.
- Company and individual license fields are evidence recorded by accountable humans; the code's eligibility guard does not claim to verify a regulator registry.
- Do not add passwords, MFA codes, private keys, or admin impersonation instructions to cases, staff notes, evidence references, or help content.
- Synthetic training examples must remain separate from live borrower files. Training content does not grant licensing, lender authority, or permission to operate; teams remain responsible for their own licensed mortgage obligations and applicable law.