Collaborations

A collaboration is what happens after a brand accepts your application or you accept a brand's invitation. It's the workspace for one paid engagement: a brief, a set of deliverables, escrow, drafts, approvals, and payout.

Active work lives at /creators/dashboard/collaborations. Click any row to open its detail view.

The list view

The list shows every collaboration you're a party to. Each card carries:

  • Campaign name — the brand's title for the brief.
  • Deliverable count — how many discrete pieces (e.g. "2 deliverables" might be a Reel plus a feed post).
  • Created date — when the collaboration was minted.
  • Status pill — current lifecycle state (see below).
  • Gross / Ripllo fee / Net to you — the money breakdown.

Lifecycle states

A collaboration moves through these states:

  • pending_funding — Created but the brand hasn't funded escrow yet. You can't upload drafts.
  • active — Escrow funded. You can submit drafts and the work is live.
  • delivered — Every deliverable has a draft uploaded and is awaiting review.
  • approved — Brand approved each deliverable (but escrow hasn't released yet).
  • paid — Escrow released; funds are on their way to your payout method.
  • disputed — Either party opened a dispute; Forjio admin will mediate.
  • canceled — Cancelled before approval.

The brand sees the same state machine from their side. Status pills are colour-coded throughout the dashboard to match.

The brief

The detail page opens with the brief — exactly the text the merchant wrote. Read it carefully; the deliverables list below it is the concrete checklist that operationalises it.

If anything's ambiguous, raise it before submitting a draft. Once you upload, the brand starts reviewing against their interpretation of the brief.

Working with deliverables

Each deliverable is one piece of content. The card shows the kind (Instagram Reel, TikTok video, blog post, UGC asset, etc.), the spec the brand wrote (length, theme, hashtags), and the current status.

Deliverable statuses

  • pending — Nothing uploaded yet.
  • draft_submitted — You uploaded; awaiting brand review.
  • approved — Brand approved this deliverable specifically.
  • rejected — Brand requested changes (with notes).
  • live — You marked it as published with a public URL.
  • metrics_recorded — Engagement data scraped post-publish.

Uploading a draft

When the collaboration is active and the deliverable is pending (or rejected after changes are requested), click Upload draft and pick a file. Accepted formats: JPEG, PNG, WebP, MP4, MOV, WebM.

Ripllo uploads the file to private S3 via a presigned PUT, then queues a watermark job. While that runs, the card shows "watermarking…". Once ready, the brand can preview the watermarked draft — the original file stays gated until they approve.

Why watermarks? Drafts ship as watermarked previews so a brand can't accept the work, ghost you, and reuse the file without paying. Approval is what unlocks the un-watermarked original.

If watermarking fails, the card surfaces the error. Re-upload — most failures are transient (corrupted file, unsupported codec).

Reviewing brand feedback

If the brand rejects a deliverable, their Merchant notes appear above the upload button. Read them, address the changes, and re-upload — the same draft slot accepts a new file in rejected state.

Marking as published

Once a deliverable is approved and you've published it on your platform (e.g. the Reel went live on Instagram), click Mark as published and paste the public URL. Examples:

  • https://www.instagram.com/reel/...
  • https://www.tiktok.com/@you/video/...
  • https://www.youtube.com/shorts/...

Status flips to live. Ripllo uses the URL to scrape engagement metrics later — drives reporting on both sides.

Approval and payout

When every deliverable is approved, the brand clicks Approve collaboration on their side. That triggers escrow release through Plugipay:

  1. Plugipay marks the funds as released.
  2. Ripllo deducts its 15% platform fee.
  3. The net amount queues for payout to whichever method you configured (bank transfer, eWallet, or PayPal — see Payouts).
  4. The collaboration moves to paid.

You'll see the net amount in the Net to you column on the list view and as Rp X on the detail header.

Disputes

If the brand rejects work that meets the agreed scope, or stops responding entirely, open a dispute. Click the Open dispute button at the bottom of the collaboration detail page and describe the issue in at least 20 characters.

A dispute freezes the escrow until Forjio admin reviews. The collaboration moves to disputed. Admin can side with either party or split the funds.

Disputes are available while the collaboration is active, delivered, or approved — not after paid or canceled.

What's next

  • Payouts — how the net amount actually reaches your bank.
  • Invitations — collaborations that started as direct invitations instead of public applications.