Team & workflow
Review & Collaboration
Collaboration built for creative ops. Spatial pins on project stills, time-aware feedback on video, editorial gates on blog posts, and role-scoped invitations , so contractors get access to what they need and nothing more.
Review Where the Work Lives
Project pins, workspace rails, blog editorial gates, and TipTap inline comments: collaboration primitives that match how studios critique, approve, and ship, not a wall of generic dashboard chips.
File review
Team clarity without enterprise bloat.
Concrete collaboration: spatial review on assets, structured project delivery, editorial discipline on posts, and access rails that scale, so advanced workflows don’t get reduced to “Roles / Invites / Activity” placeholders.
Pinned image & video review
Drop pins on stills and carry time-aware context on video in team projects: threads stay attached to the underlying project file. “That corner” and “that beat” don’t dissolve into email paraphrase.
TipTap inline comments
Blog drafts support comment mode in the TipTap editor: select text to anchor a thread, discuss in the sidebar, and resolve when your configuration enables inline comments for the post. Critique lives next to the paragraph.
Blog editorial gates
Team-aware permissions on posts: submit for review, request changes, approve, publish, so editorial staff and writers collaborate without everyone sharing one super-admin login. Publishing stays governed, not chaotic.
Project workspace rail
Buckets, workflow stages, assignments, and activity patterns built for agency-style delivery: organize selects, finals, and internal vs client-visible work in one project home. Delivery doesn’t depend on tribal knowledge.
Threads, resolve, reopen
Comment threads on project targets with status you can drive to done: reopen when creative direction shifts instead of spawning duplicate Slack channels. Decisions stay traceable on the asset.
Invitations & scoped access
Secure invites and role matrices for blog, builder, commerce, and portals: least-privilege defaults so contractors ship work without inheriting billing keys. Delegate without handing out owner keys.
Before a connected platform
- Feedback as screenshots pasted into Slack and “see attached” email chains
- Blog edits and publish rights living in one shared password
- No record of who approved a frame, a post, or a portal change last
After you standardize here
- Review pinned to pixels and timelines inside team projects
- Blog workflow and inline comments that match how editors actually collaborate
- Project buckets and stages so delivery doesn’t depend on tribal knowledge
- Invitations and roles that match how studios delegate, without enterprise bloat
Built for studio collaboration
Plyr
Video-aware review
Feedback tied to the frame and the timecode
TipTap anchors editorial comments to selected text; Resend delivers role-scoped invites; Plyr supports time-aware review on project video.
Swipe sideways for more
Collaboration systems for studios that ship
Workflows keep review, projects, and editorial moving. Clusters hold the depth behind permissions, share finals, and delivery rails.
Review on the asset
Drop feedback where it belongs: pinned threads on stills and video-aware review in team projects, so “see the frame I mean” doesn’t collapse into a wall of email.
Run the project rail
Buckets, workflow stages, assignments, and activity patterns keep deliverables moving from raw selects to finals—then share a vault link or add approved files to a portfolio.
Ship posts with editorial gates
Blog surfaces respect team permissions: submit for review, request changes, approve, and publish, so writers and editors don’t share one password to go live.
Collaborate in the editor
TipTap inline comments on drafts, comment mode, selection anchors, and a comments sidebar, when your configuration turns the feature on for the post.
Team Projects treat files as the center of conversation, not an attachment to a chat room.
- Private project storage
- Uploads signed for members—not the public media or CDN library.
- Spatial pins
- Image feedback maps to pixels, with pin-aware hover.
- Video review
- Time context beside playback—fewer “go to 01:14” scavenger hunts.
- Resolvable threads
- Comments on project files with resolve/reopen producers can audit.
Continuity across the business
The difference isn't one feature. It's what happens when publishing, commerce, media, and delivery stop behaving like separate products or plugins.
Critique is a screenshot in a chat thread
it becomes pins and threads on the actual file
Publishing is whoever has the password
editorial gates and inline comments live next to the draft
Deliverables live in folders and folklore
project workspace rails keep selects, finals, and approvals legible
Critique is a screenshot in a chat thread
it becomes pins and threads on the actual file
Publishing is whoever has the password
editorial gates and inline comments live next to the draft
Deliverables live in folders and folklore
project workspace rails keep selects, finals, and approvals legible
Ready when you are
Compare plans, then bring this surface online with the rest of your creative operating system.