Team & workflow — PixLibre

Team & workflow

Collaboration built for creative ops—not generic admin toggles: project file review with spatial pins on stills and time-aware feedback on video, team project workspaces (buckets, stages, assignments), blog editorial gates, and TipTap inline comments when your plan and settings enable them—alongside invitations and role-scoped access so contractors aren’t handed super-admin keys by default.

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.

Pinned comment threads on project stills and video—feedback lives on the frame or the timestamp, not buried under a generic attachment list.

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

On the asset

Spatial pins and video-aware review—not a wall of email

Project files carry comment context: pinned threads on stills and timestamps on video so “see the frame I mean” does not collapse into prose approximations.

Buckets, workflow stages, assignments, and activity keep selects → finals legible as crews grow
Resolve and reopen loops producers can audit later

Editorial

Blog gates plus TipTap inline comments when enabled

Posts move through submit-for-review, request-changes, and publish transitions with role-scoped permissions—writers are not forced to share one go-live password.

Comment mode anchors threads to selected text with a sidebar for threads
Clear separation between internal collaboration and public blog behavior

Signals

Activity your producers and leads can agree on

Project and file activity patterns make overnight progress legible—fewer standups spent reconstructing who moved which deliverable.

Tie comments and stage changes back to the underlying asset or post
Reduce “I thought you had the finals” gaps between production and client teams

Workspace

Buckets, stages, and assignments that survive headcount growth

Project workspace rails keep selects, finals, and internal vs client-visible work legible—delivery does not depend on tribal knowledge in chat.

Run the rail from raw capture through client-ready outputs
Activity patterns so producers know what moved overnight

Thread lifecycle

Open, resolved, and reopened decisions on the file

Threads on project targets carry status you can drive to done—reopen when creative direction shifts instead of spawning duplicate channels.

Fewer “which Slack message was the decision?” replays at color grading time
Audit-friendly loops when money or reputation is on the line

Delegation

Invites that land collaborators in the right lane

Secure invitations and scoped membership across builder, commerce, portals, and posts—delegate without handing out owner keys by default.

Writers, editors, contractors, and finance see the surfaces they need—no extra super-admin accounts
Editorial and delivery permissions stay defensible under client scrutiny

Swipe sideways for more

Systems inside systems

Grouped rails—not three repeating card sections. Workflows set rhythm; clusters carry depth.

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 without losing who said what.

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.

Spatial pins on images and pin-aware hover so feedback maps to pixels, not prose approximations
Video review paths that carry time context alongside playback—fewer “go to 01:14” scavenger hunts
Comment threads tied to project files with resolve/reopen loops your producers can audit

Publishing workflows that match how studios actually ship articles—not anonymous live edits.

Post statuses and transitions aligned to team roles (submit for review, request changes, publish) per configured permissions
TipTap inline comment mode: enter comment mode, anchor threads to selected text, and manage threads from the sidebar when comments are enabled
Clear separation between internal editorial collaboration and public-facing blog behavior

Who may touch builder, commerce, portals, and posts—without turning every contractor into an owner.

Secure invitations and scoped membership so new collaborators land with the right lane, not full tenant keys
Role matrices tuned to creative surfaces (blog, portfolio, dashboard) instead of enterprise jargon
Operational visibility—activity and audit-friendly signals where teams need accountability when money or reputation is on the line

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

Ready when you are

Compare plans, then bring this surface online with the rest of your creative operating system.

Subscribe now Documentation