Suite 05 of 7
Extend customer engagement through your ecosystem.
Support partner relationships, channel opportunities, deal registration and partner enablement through coordinated processes and shared commercial visibility.
The Partner Suite runs the partner lifecycle on two sides of one table — what the partner does and what the vendor decides — with every conflict and claim decided by a named person.
The core problem
Deal conflicts between partners and direct sales are resolved informally, so partners stop registering.
Partner tiers and eligibility are tracked outside the system that runs the programme.
Training and certification status is not visible when deals are registered.
Incentive and market development fund claims lack evidence and an approval trail.
Leads shared with partners leave the CRM and lose their consent context.
The partner lifecycle as a two-sided swimlane: what the partner does and what the vendor decides. Switch between the partner and vendor views to see each side's work.
Use the arrow keys on a step to move along the flow. The panel below the diagram describes the selected step.
Activity · Step 1 of 8
A prospective partner applies through the partner portal.
01 ActivityPartner
A prospective partner applies through the partner portal.
02 ActivityPartner manager
Agreements, contacts and onboarding steps are completed.
03 DecisionPartner manager
Tier and eligibility rules decide the programme level and its benefits.
04 ActivityPartner
Partners complete training and certifications tracked against their tier.
05 RecordPartner
The partner registers an opportunity through the portal.
06 DecisionChannel operations
Conflict rules check the registration against direct and other partner opportunities; channel operations decides.
07 ActivityPartner manager
The registered opportunity is worked together with direct sales in the Sales Suite.
08 Hand-offiShield One
to: iShield One
Approved incentive and fund claims hand off to iShield One for accruals and payment. This hand-off depends on how the platforms are implemented and configured.
01 ActivityPartner
A prospective partner applies through the partner portal.
02 ActivityPartner manager
Agreements, contacts and onboarding steps are completed.
03 DecisionPartner manager
Tier and eligibility rules decide the programme level and its benefits.
04 ActivityPartner
Partners complete training and certifications tracked against their tier.
05 RecordPartner
The partner registers an opportunity through the portal.
06 DecisionChannel operations
Conflict rules check the registration against direct and other partner opportunities; channel operations decides.
07 ActivityPartner manager
The registered opportunity is worked together with direct sales in the Sales Suite.
08 Hand-offiShield One
to: iShield One
Approved incentive and fund claims hand off to iShield One for accruals and payment. This hand-off depends on how the platforms are implemented and configured.
Each capability: its purpose, what it covers, who decides, the records it keeps and how exceptions are handled. Functions included in a deployment are agreed during solution design.
Capability 1 of 3
Run the partner programme from application to tier.
Previously listed as
The partner manager onboards partners and assigns tiers under programme rules.
Capability 2 of 3
Let partners register deals and sell alongside your team without conflict.
Previously listed as
New capability in the Suite structure.
Channel operations sets conflict rules and decides contested registrations.
Capability 3 of 3
Keep partner training and certifications current, and reward partners on evidence.
Incentive payments, accruals and partner payables stay in iShield One.
Previously listed as
New capability in the Suite structure.
The partner manager approves incentive claims. Finance in iShield One pays them.
“Partners act; the vendor decides; every decision has a reason.”
Trigger: Registration overlaps an existing opportunity
Who acts: Channel operations
The decision and its reason are recorded on the registration.
Trigger: Partner below tier criteria
Who acts: Partner manager
The partner is held, not silently downgraded.
Trigger: Incentive claim without proof
Who acts: Partner manager
Rejected with the reason before any payment.
Rules and automation
Programme rules owned by channel operations.
Not offered
Decisions that stay with people.
iShield Connect owns CRM and customer engagement. Each other platform keeps its own responsibility.
The Partner Suite owns
Partner accounts, tiers, registrations, conflict decisions, co-selling, enablement records and incentive claims.
Owns
Incentive and fund payments, accruals and partner payables stay in iShield One.
Owns
Connections to partner systems are provided through iShield Link where implemented and configured.
Owns
Where an organisation runs iShieldGRC, third-party risk and anti-bribery programmes sit there.
These boundaries describe how responsibilities are intended to divide between the platforms. Integration depth depends on how they are implemented and configured.
Measures teams can follow where configured. Names only: targets and results belong to each organisation.
Registrations by status
From Deal Registration & Channel Sales
Conflicts decided
From Deal Registration & Channel Sales
Partner-sourced pipeline
From Deal Registration & Channel Sales
Partners by tier
From Partner Relationship Management
Certifications current
From Partner Enablement
Claims by status
From Partner Enablement
How the Suite relates to recognised standards. This describes alignment of practice; conformity and certification belong to each organisation.
ISO 37001 — anti-bribery management systems
Context for incentive and fund controls; the management system belongs to each organisation.
ISO/IEC 27036 — supplier relationship security
Context for sharing customer data with partners.
GDPR · UAE PDPL · KSA PDPL
Applies to the customer's use: controller and processor roles when leads are shared with partners.
Recruit, enable, sell — with the vendor's decisions visible at each stage.
Who joins the programme, at which tier?
Accountable: Partner manager
Are partners ready to sell and support?
Accountable: Partner manager
Which deals do partners own, and how do we sell together?
Accountable: Channel operations · opportunity owner
We use strictly necessary storage to run this website. With your permission we also use first-party analytics to understand which pages are useful. Analytics stays off unless you choose "Accept all" or turn it on in "Manage". You can change your choice at any time from "Cookie settings" in the footer. See our Privacy Policy.
