Content approvals let a creator send draft content to a brand for sign-off before it goes live, and let the brand approve it or ask for changes — all on one screen, with the feedback attached to the exact piece of content it’s about.
The loop
The creator opens the calendar event the content belongs to and creates an approval request.
They add one or more deliverables — a Reel, a story, a blog post — each with its own caption, preview link and files.
They send the request. Everyone they listed as a reviewer gets an email with a link straight into the request.
The brand approves each deliverable, asks for changes, or rejects it.
If changes are requested, the creator updates the deliverable and hits Resubmit for review, which puts it back in front of the brand.
Once everything is approved, the creator is clear to publish.
Creating a request (creator)
Approval requests live on a calendar event, so start there.
Open the event in your editorial calendar.
Click Content Approvals in the event’s header.
Fill in the request:
Who should review this? — one or more email addresses, comma-separated. If the event came from a brand collaboration, we pre-fill the brand’s reviewers for you.
Title — defaults to the event name.
Notes for the reviewer — the brief, the posting date, or what you’d specifically like feedback on.
Needed by — optional deadline.
Click Create request.
Adding deliverables
From the request, click Add deliverable for each piece of content. Each one takes a title, a description, the caption you plan to post, an optional preview URL, and any files (images or video) you want reviewed. Files show up as a preview on the card, so the reviewer can watch or scroll through them without downloading anything.
When everything is on the request, click Send for review. Each reviewer we can reach gets their own email with a link straight into the request, and they don’t need a paid plan to review your content. If we can’t reach one of them we’ll say so on screen — see “If a reviewer can’t be reached” below.
Reviewing (brand)
Open the link in the email, or find the request from the collaboration in your campaign. The top of the page tells you how many deliverables are waiting on you.
On each card you can:
Approve — signs off on that deliverable. A note is optional.
Request changes — opens a note field on the card. The note is required, and it’s what the creator works from, so be specific.
Reject — for content that can’t be used at all. A note is required here too.
Every action happens in place. You never leave the page, and you never lose your scroll position part-way through a list.
If several deliverables are fine as-is, use Approve all at the top to sign off on everything still waiting on you in one click. It sends the creator a single summary email rather than one per deliverable.
Changed your mind? Undo decision puts the deliverable back under review and tells the creator their earlier result no longer applies.
Acting on feedback (creator)
Feedback appears directly on the deliverable it’s about, on its card — not in a separate thread you have to match up by hand. A deliverable with changes requested is outlined in amber and shows the reviewer’s note underneath.
Update the deliverable (edit the caption, swap the file, whatever they asked for), then click Resubmit for review. That’s the step that notifies the brand — editing on its own doesn’t, so you can work on a fix over several sittings without pinging them each time.
One exception: if you edit a deliverable the brand has already approved, the approval is withdrawn automatically and the brand is told the content changed. Their sign-off applied to the version they saw.
Statuses
Status | Meaning |
Draft | Not sent to the brand yet |
In review | Waiting on the reviewer |
Changes requested | Waiting on the creator to fix and resubmit |
Approved | Signed off — clear to publish |
Rejected | Can’t be used |
Discussion vs. feedback
Each request also has a Discussion thread at the bottom for anything that isn’t about one specific deliverable — scheduling, a question about the brief. Feedback that is about a deliverable should go through Request changes on that card, so it stays attached to the right piece of content.
Writing useful feedback
Specific:
“Please add the hashtag #BrandPartner”
“The product should be more visible in the first image”
“Add the disclosure at the start of the caption, not the end”
Not specific:
“This doesn’t work”
“Try again”
If a reviewer can’t be reached
When you send a request, we look up each reviewer’s email. If someone already has an InfluenceKit account, the request goes to them. If nobody on your list has an account yet, we set one up for the brand and everyone you listed gets in.
What we won’t do is add a new person to a brand’s existing account. If the brand is already on InfluenceKit and you list a colleague of theirs who isn’t, we’ll tell you we couldn’t reach that address — ask someone at the brand to invite them, then they’ll be able to review. This is deliberate: anyone could type any address into that box, so we don’t hand out access to a company’s account on the strength of it.
Notes
Reviewers don’t need a paid InfluenceKit plan. Reviewing content you were invited to review is always free.
An event can hold more than one approval request — use New request on a request to start another, and All requests to move between them.
Everyone listed as a reviewer gets notified, not just the first person.