Operating
The creator portal
Everything a creator sees, in the brand's colours rather than ours. Three surfaces, and they are all the same brand to the person looking at them.
Apply — /apply/<campaign>, public, no sign-in. The form a campaign sends
people to. It writes a pending application; nobody becomes a creator by
submitting it.
The hub — /c/<campaign>, one campaign, a left rail of tabs: Submit,
Resources, Community, Content bank. This is where a campaign is actually run.
Home — /home, behind a sign-in. Every campaign a creator is on, their
handles and links, and the way into each hub. A creator on one brand sees that
brand's colours; a creator on two sees ours and each brand's within it.
Set a campaign up
1. Branding. One colour and a logo on the account, under Settings. Every public surface merges them over a neutral base, so this is the whole of making the portal look like the client rather than like us.
2. Hub content. Open the campaign, then Creator hub at the bottom of the editor. Four kinds:
Announcement — dated notices. Payout changes, deadlines, a new brief.
Guide — prose written to be read start to finish. What makes a clip pay.
Link — somewhere to go. The brief, the tracker, a form.
Content bank — b-roll, logos, hooks that worked, posts to model.
Leave the campaign blank on a resource and it appears on every campaign that client runs — use that for anything evergreen.
A tab you have not filled does not appear. An empty Resources tab is worse than none, so the rail only shows what has something behind it. A portal with one tab means nothing has been put in it yet, which is the state every new campaign starts in.
3. Community URL. On the same page. Discord or Whop. It is what makes the Community tab exist.
4. Open applications. On the campaign itself.
Reviewing
Applications land on Creators. Approving does four things, in this order, and the order matters because each needs the one before it:
Creates the creator and the social account, if the handle is new.
Issues their tracking link.
Creates their Acrune account from the address on the application.
Emails them a sign-in that lands on their portal.
Turning somebody down asks for a reason. It is kept on the record rather than sent, so write it for the next person to read the queue.
An application with no address
Everything before the form asked for an email has none. Those can still be approved — the creator and the link are real and start earning immediately — but nobody can be told, because there is nowhere to send it. The reviewer sees which case they are in before deciding.
If the invite does not go out
The decision still stands: the approval is written and the link works. You get
a line saying the sign-in was not sent. That happens when WEBHOOK_SECRET is
missing from the dashboard's environment, or the apex is unreachable. Nothing
about email can undo an approval, by design — the access is real either way.
What a creator can do
Sign in at acrune.com with the address on their application. Their portal carries their campaigns, their links, what they have submitted and what was decided about it, and whatever the brand has put in the hub.
They have one account across every brand they work with, and one row per brand behind it. Signing in once shows them all of it.