Your partners arrive with their tier and history already attached. What is left is deciding who joins, what rung they sit on, and how much of your pipeline each role is allowed to read.
Your partner list is already populated, with tiers, owners and deal history attached. The useful first pass is subtractive: filter for partners with no activity this year and archive the ones who left the program without ever leaving the CRM.
Archiving keeps the history and removes the partner from the live roster, so your numbers stop being flattered by accounts that stopped selling two years ago.
Open a partner organisation and invite its users individually, each with the role they should join on. A partner admin manages their own team and registers deals. A partner member registers deals and reads collateral but cannot change who else has access.
When an invited user lands, a guided tour walks them through the interface scoped to their role, so nobody has to work out where anything lives.
Build the ladder once: the rungs, the number that qualifies a partner for each rung, and the commission that rung pays. Attach an MDF accrual percentage to any rung that should earn funds.
After that it runs itself. Airstride recomputes a partner's tier the moment a deal is won, and a scheduled sweep re-evaluates the whole roster so a partner who has gone quiet does not keep drawing top-tier margin. The rate follows the rung, which is what separates a tier from a badge in a slide deck.
Roles decide what someone can do. Your own team sees the whole program. A partner admin manages their team and their own pipeline. A partner member registers deals and reads collateral. No partner role can see another partner, and none can edit tiers or commission.
Underneath the role sits field-level permission, which decides which fields that role can read: stage, value, customer contacts, custom fields and internal notes. Both layers are enforced in the portal, in the API and in every export, so there is no back route to a field a role cannot see.
Nobody self-serves their way in. There are exactly two routes, and you own both.
No. There are two gates and both are yours. A partner organisation goes live only after you approve its onboarding application, and a user joins an existing organisation only by invitation with a role attached.
A role decides what someone can do: register a deal, invite a teammate, read a document. A tier decides what a partner organisation earns: the commission rate and the funds they accrue. Roles are about permission, tiers are about economics.
No. Airstride recomputes a partner's tier the moment a deal is won, and a scheduled sweep re-evaluates the whole roster so nobody sits on a tier they no longer hold. Promotions and demotions both happen without anyone running an export.
Yes. Field-level permissions are applied per partner role, so a strategic partner can see deal value where a referral partner cannot. The animated version of that screen is in connecting your CRM.
Yes. Roles and field-level permissions are enforced in the portal, in the API and in every export. There is no route to a field a role cannot read.
A portal under your brand, populated with their own deals and their own collateral, plus a guided setup checklist scoped to their role. The checklist disappears once their configuration is done.
We will show you the roster, the tiers and the permission model on your data rather than a demo tenant.
