Introducing the Siren Collaborator Portal
A look at the standalone front-end portal that shipped with Siren 3.0. Branded, block-based, powered by the WordPress editor. Partners log in to a dashboard that belongs to your site, not to wp-admin.
Siren 3.0 ships with a new Collaborator Portal. It’s a front-end dashboard where your partners log in to a page that belongs to your site, not WordPress. We built it because when the partners you’re paying are creators or influencers, wp-admin is the wrong place for them to spend time.
It’s the Siren 3.0 feature I’ve been waiting longest to ship, because every other Siren surface could live inside WordPress. This one had to live inside your site.
The portal ships with Siren Essentials and above. On Siren Lite, collaborators use a simpler Collaborator Dashboard inside wp-admin, with the same data in a plainer surface.
Day one in a collaborator’s seat
Dashboard
The portal opens on a clean dashboard. The top shows a rewards summary split into paid, unpaid, and rejected. A creator running a 12-store coupon-based program glances at that and immediately knows where she stands this month. If a payout is on the way, it shows up here too, so she isn’t asking you when the next check hits.
Earnings
The Earnings view breaks those numbers down further. A six-month chart of earnings over time, recent commissions tagged with their status, and a payments log showing what’s already been paid out. When a collaborator wants to reconcile a specific commission against the order she remembers, she finds it without opening a support ticket.
Performance
Engagement stats are broken down by time period (today, this week, this month) and by program. If a collaborator sits in multiple programs, each one gets its own line, which matters for a marketplace vendor enrolled in both the standard affiliate program and a bonus-driven holiday push. This is the view that turns “how’s it going?” into a conversation with real numbers in it.
No more DMs asking for the referral link
The portal handles the self-serve pieces that used to be the reason collaborators emailed you.
Referral URLs
A URL generator takes any page on your site and returns a referral link with the collaborator’s code already attached. Paste in the product page for a new launch, hit generate, copy the link. No more DMs asking “can you send me the referral link for the new launch?” They get it themselves, the same moment the post goes live.
There’s also a “Get Referral Link” button in the WordPress toolbar. If a logged-in collaborator is browsing your store, she grabs a referral link for the exact page she’s on with one click. It’s a small piece of convenience that ended up mattering a lot for high-volume collaborators sharing a broad catalog across platforms in the same week.
Coupons
A coupon section shows any codes assigned to the collaborator, ready to share. Codes show up the same way links do, in a format they can lift into a post or a story. When a customer uses one at checkout, Siren tracks the coupon engagement and ties the conversion back to the code’s owner. For a coupon-based creator program, think 15 Instagram creators posting try-on hauls with their own discount codes, this is the product as far as the creator is concerned. They never see Siren. They see your brand, their codes, and their earnings.
Profile
A Profile view rounds the portal out. Collaborators update their display name, see the referral code attached to their account, and confirm their status without pinging support. It’s the kind of thing nobody writes home about until they don’t have it.
Make it look like your site, not like WordPress
The portal replaces your theme entirely when a collaborator visits, which means it needs its own look. Three layers of control decide what that looks like, and they stack on top of each other.
Global Styles (the automatic path)
If your WordPress theme supports Global Styles (most block themes do), the portal reads three values automatically: background color, text color, and accent color. If you’ve already customized your theme in Appearance, Editor, Styles, you’re done. The portal picks up your brand without you touching a single portal-specific setting. The Customizing the Collaborator Portal docs walk through every branding option in detail. Picture a Shopify-refugee outdoor apparel brand whose site runs on an olive-green-and-bone-white palette. They open the portal preview expecting to configure colors and find their existing palette already carried through. No portal-specific settings touched. That’s the case the layering is built for.
Portal Branding panel (block-editor overrides)
If you want the portal to look different from the rest of your site, the Portal Branding panel in the block editor overrides Global Styles for the portal only. Set background, text, and accent colors directly. Add a sidebar logo URL to replace the default icon with your own mark. Every change previews live in the editor, the same way any other block does.
Shortcode (for classic themes)
For classic themes that don’t run the full site editor, a shortcode exposes the same attributes. Same branding result, different insertion point.
The layering is deliberate. Most operators never need to touch anything past Global Styles. The ones who want tighter control get the block-level overrides. The ones on classic themes get the shortcode. Nobody gets stuck.
The finished portal reads as a page of your site, not as a plugin dashboard pretending to be one.
When the default strains against your program
The default portal is opinionated. It assumes the collaborator is a fairly standard partner earning commissions on referrals. That’s the common case, and the default serves it well.
The strain shows up when the “collaborators” aren’t standard partners. An outdoor-apparel brand running a donation-per-purchase program with a coastal conservation nonprofit needs a dashboard scoped to donations received this quarter, not commissions paid this month. A course platform paying instructors based on student engagement needs course and lesson completion graphs, not referral-link counters. A marketplace where 80 vendors want to see which of their own products sold in the last 30 days needs a per-vendor product view the default doesn’t know about.
That’s what the full REST API is for. Teams running unusual programs build their own dashboard against the same data Siren exposes to the default, and use the portal block as a layout shell or replace it entirely. The default isn’t a ceiling. It’s the starting line.
When to stay on Lite, and when to upgrade
Worth restating because the two surfaces look different enough to matter. On Siren Lite, collaborators open a Collaborator Dashboard inside wp-admin. Earnings, referral links, coupons, and obligation history are all there, rendered in WordPress’s admin styling. For first programs and lower-volume setups, that’s often exactly right.
The branded front-end portal described above ships with Siren Essentials and above. If you want the page partners log into to match the rest of your site, that’s the tier where the branded portal lives.
See it on your theme
The fastest way to know whether the portal fits your brand is to see it running on your site. Drop the Collaborator Portal block on a staging page, point a test partner account at it, and open the page in your browser. You’ll know in about thirty seconds whether the Global Styles carry-through does the work you need, and you can go from there.
Get Siren if you haven’t already.