Collab Projects
Manage collaboration workflow areas inside a project, including Production, Post-Production, Distribution, roles, access scopes, and common issues.
What you can do inside a project
The collaboration workflow page at /collab/{id} is organized into three stages. Each stage groups the tools you need at that point in the project.
Use Production for planning, setup, and active coordination.
-
Overview keeps the project goal, scope, and context in one place.
-
Collaborators shows who is involved and what access they have.
-
Compliance tracks verification, agreements, and release-related work.
-
Timeline keeps schedule details and key dates close to the project.
-
Moodboard organizes visual references and creative direction.
-
Screenplay keeps script or scene planning available to the team.
Use Post-Production for working assets and service support after production work begins.
-
Project Files is where you exchange working files, dailies, references, and deliverables during production and post.
-
Pro Services appears in this stage when you need to locate service-related options connected to the project workflow.
Use Distribution for delivery preparation, asset context, and downstream usage details.
-
File Sharing is the distribution-stage area for sharing approved or delivery-ready files.
-
Metadata captures delivery context that helps identify and organize assets.
-
Credits keeps attribution details close to the project.
-
Licensing describes how approved assets can be used.
-
Forensics & Distribution groups distribution and forensic review surfaces where available.
Project Chat is available from the project header rather than as a workflow tab. Collaborator Project Chat access is enabled automatically and is not user-toggleable per invite.
Different stages may matter more depending on your role. Owners typically focus on collaborators, compliance, and distribution readiness, while contributors may spend more time in Project Files and Project Chat.
Roles, ownership, and access scopes
Different people see the same collaboration through different lenses, but the feature centers on project owners/senders and collaborators/receivers, with behavior shaped by Compliance Role and Access Scope.
Focus: Create the proposal, choose collaborators, and control access and status.
-
Start new projects from
/collabsand configure the Overview before sending invites. -
Use the invite UI to search profiles or send email invites, choosing On-Screen or Off-Screen Compliance Role and a Viewer, Contributor, or Editor Access Scope intentionally.
-
Monitor proposal status using the UI labels Pending, Accepted, Completed, and Archived, then update it as the project moves forward.
-
Adjust collaborator roles and access scopes when responsibilities change instead of sharing accounts.
-
Close out projects by marking them Completed and archiving them when they are no longer active.
Focus: Respond to collaboration requests and contribute within your assigned role and access scope.
-
Watch for collaboration request notifications or email invites linking to the project.
-
Review the Overview and, where applicable, Compliance details before accepting.
-
Check your Compliance Role and Access Scope in the Collaborators tab:
-
Viewer is for read-focused collaborators who need project visibility.
-
Contributor is for collaborators who provide materials, references, or deliverables.
-
Editor is for collaborators who help manage more of the project workflow.
-
-
Use Project Chat for questions and clarifications instead of separate channels. Project Chat access is locked on for collaborators.
-
Let the owner know if your role or access scope does not match what you need to do the work.
Focus: Keep everyone aligned on what the collaboration space represents.
-
Treat
/collab/{id}as the source of truth for project context, files, and decisions. -
Use the Collaborators tab, not manual lists, to understand who has access.
-
Expect that ownership stays with the sender: they control status changes and archiving.
-
Use Access Scope as a guide for behavior: do not work around a limited scope by asking others to upload or change items on your behalf.
Access, privacy, and compliance
Collabs projects are shared workspaces, not public content. Only people explicitly added as collaborators on a project should see its internal details.
The invite UI now centers on role and scope rather than separate View, Comment, and Upload toggles:
-
Compliance Role – choose On-Screen for collaborators who appear in the content, or Off-Screen for collaborators who support the project without appearing in it.
-
Access Scope – choose Viewer, Contributor, or Editor based on how much project participation the collaborator needs.
-
Locked capabilities – View Only Mode, Stream Release Assets, and Project Chat Access stay enabled automatically and cannot be toggled per invite.
Use Viewer for visibility, Contributor for people providing materials or deliverables, and Editor for collaborators who help manage the workflow. Grant broader scope only when it is necessary.
Respect privacy when you include personal information, images, or project details in a collaboration.
-
Keep sensitive information (for example, IDs, private contact details, rates) limited to projects and collaborators who actually need it.
-
Use the Compliance tab to keep verification or agreement-related information close to the project, but do not treat it as a substitute for your own record-keeping.
-
Remember that external email invites may expose the project title and basic context in the email; write titles and descriptions accordingly.
This documentation does not provide legal advice. For questions about consent, releases, IP ownership, or regulatory obligations, involve your legal or compliance team before you publish or reuse collaboration assets.
Common issues and how to handle them
When a proposal stays Pending, the receiver may not have seen or acted on the invite.
-
Confirm that the collaborator’s email or profile you invited is correct in the Collaborators tab.
-
Ask the collaborator to check their in-app notifications for a collaboration request.
-
If you used email, ask them to check their inbox and spam folder for the external invite.
-
Resend the invite or create a new one if you suspect the original email address was wrong.
If the collaboration needs to move ahead with someone else, update the invite list rather than reusing the same pending entry.
Sometimes receivers accept from email or notifications but still are not sure where to go.
-
Ask them to open
/collabswhile logged in with the same account that received the invite. -
Confirm that the proposal is Accepted and that their profile appears in the Collaborators tab.
-
Share the direct
/collab/{id}link with them once they have account access.
If the project still does not appear, verify that they did not accidentally use a different email or account when signing up.
If someone cannot perform an action you expect, check their role and scope on the project.
-
Open the Collaborators tab and review their Compliance Role and Access Scope.
-
Move them to Viewer, Contributor, or Editor based on the work they need to perform.
-
Confirm whether they should be On-Screen or Off-Screen for compliance handling.
-
Remember that View Only Mode, Stream Release Assets, and Project Chat Access are locked on for collaborators.
-
Save changes and ask them to refresh the
/collab/{id}page.
Avoid sharing files or feedback through side channels as a workaround; update the role or scope so the work happens in the project.
External invites send a branded email with a link, such as /communications?proposal={id}, so the recipient can respond.
-
Ask the recipient to follow the link from the email and complete any required signup or login.
-
Once they create a ModelBoard account with that email, the proposal links to their user profile.
-
They should then see the collaboration request in their notifications and
/collabs.
If they signed up with a different email than the one you invited, send a new invite to the email tied to their account.
Completed work that still appears active can clutter your /collabs hub.
-
Review the project on
/collab/{id}to confirm assets and communication are up to date. -
Mark the project Completed when the main work is finished.
-
Archive the project so it no longer appears in your active list but stays available for reference.
Keeping statuses accurate makes it easier for everyone to see which collaborations still require attention.