Collaborators & Presence
Invite people to a project, give them a lane, and see each other's cursors live while you edit.
A project can have a team. You invite people, give each a role, and when you're in the editor at the same time you can see where everyone is.
Inviting people
Invite a collaborator to a project by their GitHub username or their email. Klipeo creates a shareable invitation link where they can Accept or Decline once they're signed in. Copy that link from the collaborator list and send it to them; email invitations are also sent automatically when email delivery is configured.
The collaborator list shows both the Klipeo membership state and whether GitHub access is pending, active, failed, or removed. You can retry a failed GitHub invite, re-invite someone who declined or was removed, and remove a collaborator at any time. Inviting is rate-limited to 30 invites a minute per signed-in account, so a runaway script can't spam anyone.
Klipeo only removes repository access that it created. If someone already had access before the Klipeo invite, declining or removing the Klipeo membership leaves that independently managed GitHub access alone. If GitHub is temporarily unavailable, Klipeo leaves the membership recoverable instead of claiming access was removed.
Roles
Each collaborator gets a role that says what they're there to do:
| Role | Lane |
|---|---|
| Owner | The person who created the project |
| Lead | Running the edit — everything is fair game |
| Video & cuts | Video and graphic tracks, cuts and timing |
| Audio | Audio tracks |
| Text & credits | Text and title tracks |
| VFX | Effect tracks |
| Color grading | Canvas backgrounds and beautify settings |
Roles are lanes, not locks
A role doesn't restrict anything. Everyone works on their own branch and can edit anything on it — the role tells the rest of the team what to expect from you, and the Collaboration dock spells out your lane with a note that cross-lane edits are allowed but discouraged. If you need hard enforcement, that's what pull request review is for.
Everyone who has accepted an invite — not just the owner — can commit, pull main, and publish to main on their own branch.
Live presence
When more than one of you is in a composition, the editor header shows an active
editors chip: up to four avatars, plus a +N when there are more. Each person gets
one of six accent colors, and you'll see their playhead cursor on the timeline at
whatever position they're playing from.
Your editor sends a heartbeat every 5 seconds, and someone drops off the list about 30 seconds after their last one — so a tab that goes quiet or a person who closes the editor disappears shortly after.
Presence vs history
Presence is the live picture of who's here this second. The lasting record of who changed what lives in the project's GitHub history, in branches and commits. The two work together: edit live, then publish through a pull request.