Compliance tab
Track release forms, 2257 verification, and boundaries and consent for each collaborator in a Collab project using the Compliance tab.
Where the Compliance tab lives
Open the Compliance tab from any Collab project workflow to track required documentation and agreements for everyone involved in the project.
- Go to your Collabs hub at
/collabs. - Select a project to open the workflow page at
/collab/{id}. - Switch to the Compliance tab in the project header.
The Compliance tab is vAulth-branded and focuses on project compliance tracking rather than showing raw legal documents.
The Compliance tab integrates with vAulth to verify documentation, collect release form signatures, and support automated 2257 signature delegation. Sensitive documents stay encrypted and are not displayed directly in the UI.
What the Compliance tab shows
The Compliance tab is organized into two main parts:
- A release form signing section for the project as a whole.
- Per-collaborator compliance cards for 2257 documentation, automated signature authorization, boundaries and consent, and QR scan activity.
Release form signing section
The release form signing section tracks who has signed the project release form and when the project-level form is ready to generate or download as a signed PDF.
You see:
- A signature progress indicator such as
2 of 4 signed. - A signer list with each collaborator, their role, and signed status.
- A self-sign action that opens a modal to add your legal name, contact details, role, and signature.
- A Generate PDF action after all required signatures are complete.
- A Download action after the signed PDF is generated.
- A Pro Only or Awaiting Signatures state when the account or project is not yet eligible to generate the final PDF.
After everyone signs, use Generate PDF to create the final release form. When generation finishes, Download creates a fresh signed link for the stored PDF instead of relying on an older View action.
Collaborator compliance cards
Each participant in the project has a compliance card showing their verification state and available actions.
Every card includes:
- Avatar and name.
- A You badge on your own card.
- Separate mini-cards for:
- 2257 documentation and signature authorization.
- Boundaries and consent.
- QR scan status (for other collaborators).
The UI surfaces encrypted or tamper-proof indicators, authorization state, and verification links instead of raw document contents.
Recommended workflow for project owners
Use the Compliance tab throughout the lifecycle of a Collab project to keep documentation on track.
Confirm required signers
Open the project at /collab/{id} and switch to the Compliance tab. Review the release form signer list and confirm that all required participants appear with the correct roles before you start collecting signatures.
Sign your own release form
Find your entry in the release form section and use the self-sign action to open the signing modal. Enter your legal name, contact details, role in the project, and signature, then submit to update your signed status.
Monitor signature progress
Watch the signature progress indicator to see how many collaborators have signed. Use the signer list to follow up with anyone still pending and keep the project timeline aligned with your shoot or delivery schedule.
Verify 2257 documentation per collaborator
In each collaborator card, check the 2257 documentation status. Use the verification action to route collaborators through vAulth if their documentation is missing or unverified, and confirm that their status updates to verified and encrypted.
Review automated 2257 signature authorization
Check whether collaborators have authorized automated 2257 signature delegation during verification. If a collaborator has not authorized the flow or later revokes it from settings, route them back through the appropriate vAulth or account settings flow before relying on delegated signatures.
Collect boundaries and consent
Review the boundaries and consent status for each collaborator. Complete your own consent form where required, and use reminder actions to prompt others whose status shows action required or missing.
Use QR scans on set or in person
When working in person, use the QR scan option on unverified collaborators to open the scanner modal. Scan their QR code to record the event in the project's QR scan history and keep an auditable record of in-person verification.
Generate and download the fully signed release form
After all required signers complete the release form, use Generate PDF from the Compliance tab. When the action changes to Download, download the signed file through the fresh signed link and store it with your project records alongside any internal archives.
Compliance items and statuses
These are the key compliance elements you track on the Compliance tab and how to interpret them.
Release form and signatures
Overall release form status for the project, shown as counts such as 2 of 4 signed. Use this to see at a glance how many required signers have completed their part.
List of collaborators expected to sign the release form. Each entry includes the collaborator name, role, signed or pending status, and the signed date when available.
Dialog that lets you sign your own release form entry by providing your legal name, contact information, role in the project, and signature. Submitting updates your record in the signer list.
Current release form button state. Common states include Generate PDF when all signatures are complete, Download after the PDF is ready, Pro Only when the account does not have the required access, and Awaiting Signatures while required signers are still pending.
Downloadable project release form generated after all required signatures are collected. The generation action stays disabled until signature progress is complete, and the download action creates a fresh signed link for the stored PDF.
2257 documentation and signature delegation
Overall 2257 documentation state for a collaborator. Typical states include verified and encrypted when documentation is on file and validated, or missing when no documentation is attached yet. When verified, the UI may display a tamper-proof hash and verification public key.
Optional technical details attached to verified documentation, such as a cryptographic hash and a corresponding public key used to confirm that the record has not been tampered with.
Action that starts the vAulth verification flow for a collaborator whose 2257 documentation is missing or unverified. This flow handles identity checks, document upload, and any required 2257 signature authorization outside of the core project UI.
Audit-style history of delegated 2257 signature activity. Use this to confirm when an automated signature was applied and whether the action came from an active authorization.
Boundaries and consent
Status of the boundaries and consent information for a collaborator. Common values include completed when all required questions are answered, action required when some steps are still pending, or missing when no form has been submitted.
Interactive form that collaborators complete to record their boundaries and consent preferences for the project. You complete your own form through your card; you do not fill this on behalf of others.
Action available on other collaborators' cards to send them a reminder when their boundaries and consent status is action required or missing.
QR scans and in-person verification
Control on another collaborator's card that opens a QR scanner modal when their compliance status is unverified. Use this during in-person sessions to scan their QR code.
Project QR scan history associated with the project. Each entry links a scan event to a collaborator to provide an auditable trail of in-person verification activity.
The Compliance tab indicates whether documentation is encrypted or tamper-proof and exposes only verification results, authorization state, activity summaries, and links. It does not show underlying identification documents directly.
Legal disclaimer
Compliance information in ModelBoard, including 2257 status, boundaries and consent records, release forms, automated signature delegation, and vAulth integration, is provided to help you organize and track documentation. It does not constitute legal advice and does not guarantee that your project satisfies all applicable laws or regulations. Consult your own legal counsel to understand your obligations and ensure your use of this tool aligns with the requirements in your jurisdiction.
Troubleshooting and FAQs
The signed PDF controls depend on signature progress, account access, and whether the PDF has already been generated.
Check that:
- The signature progress indicator shows that every required signer is marked signed.
- The button shows Generate PDF before you expect Download.
- The button does not show Pro Only, which means the project needs the required account access before generating the PDF.
- No collaborators have been removed and re-added without signing again.
- You refreshed the page after the last signature to allow the button state to update.
If all signers appear signed, click Generate PDF first. When generation completes, use Download to create a fresh signed link for the PDF. If the issue continues, contact support and mention the current button state in the Compliance tab.
When a collaborator's 2257 status shows as missing, ask them to complete the verification flow using the 2257 section on their compliance card.
You can:
- Use the verification action on their card to route them through vAulth.
- Ask them to review and authorize automated 2257 signatures if the verification flow requires it.
- Confirm that their status updates to verified and encrypted after they complete the flow.
If the collaborator reports issues in the vAulth flow, have them check their connection and identity details, then retry from the Compliance tab.
Revoking authorization stops future delegated 2257 signatures from being applied through that authorization. It does not remove the need to keep 2257 documentation current for the project.
Ask the collaborator to open account settings if they need to review or change their authorization state. For audit questions, use the automated signature activity history to confirm which delegated signatures were applied before revocation.
A status of action required usually means the collaborator started but did not submit the full boundaries and consent form.
Ask the collaborator to:
- Reopen the form from their compliance card.
- Review any incomplete sections or required questions.
- Submit again until the status updates to completed.
You can send a reminder from their card to prompt them if they have not returned to finish the form.
The QR scan option only appears for other collaborators when their status requires verification and when a QR-based flow is available.
You might not see the QR scan action if:
- You are viewing your own card.
- The collaborator is already fully verified.
- The project does not require QR-based in-person verification for that collaborator.
If you still believe a QR scan should be available, confirm the collaborator's current compliance status and project requirements before contacting support.
Where to go next
Use these related pages to understand the rest of the Collab workflow around the Compliance tab.
Collaboration Hub overview
See how /collabs organizes all your projects and how the workflow at /collab/{id} connects tabs like Overview, Collaborators, Compliance, and more.
Manage collaborators
Learn how to add collaborators, adjust roles, and control who appears in the signer list and on compliance cards for each project.
File Sharing
Move assets between collaborators, keep track of versions, and see how file sharing connects to compliance and licensing for each project.
Licensing
Understand how to manage licenses, usage rights, and downstream distribution for assets created in your Collab projects.