Skip to main content
Zentium Technologies
Case study

A partner portal with a sharing model that passed security review

Replacing an email-and-spreadsheet partner process with a branded Experience Cloud portal — deal registration, pipeline visibility and document access, on a least-privilege sharing model.
Client
Confidential — B2B technology
Published
April 22, 2026

Single

System of record for deal registration

Self-serve

Partner pipeline visibility

Least privilege

Sharing model by design

Challenge

What was going wrong

Partner deal registration ran on a shared inbox and a spreadsheet. Conflicts over deal ownership were resolved by whoever could find the earliest email.

Partners had no visibility of registered deal status, so the channel team fielded a steady stream of status-check requests.

An earlier portal attempt had been halted when a security review found guest-user access exposing records beyond the partner's own account.

Approach

How we built it

  • 01

    Access model first

    Licence types, account-role hierarchy, sharing sets and permission-set groups were designed and reviewed before any page was built, with guest-user access hardened to the minimum required.

  • 02

    Deal registration workflow

    Registration with automated conflict detection against existing opportunities, approval routing to the channel team, and expiry rules on protected deals.

  • 03

    Branded front end

    Custom theme layouts and Lightning Web Components built against the client's design system, so the portal reads as part of the product rather than a bolt-on.

  • 04

    Self-service visibility

    Partners see their own registered deals, pipeline status, enablement documents and support cases — scoped strictly to their account.

Architecture

How the pieces fit together

  1. Partner Community licences with account-role hierarchy driving record visibility

  2. Sharing sets scoping records to the partner's own account

  3. Guest user profile stripped to the minimum object and field access

  4. Deal registration built in Flow with duplicate detection and approval routing

  5. Custom LWC components consuming Apex with enforced CRUD and field-level security

Stack

  • Experience Cloud
  • Partner Community
  • Sharing Sets
  • Lightning Web Components
  • Flow
  • Apex with USER_MODE

Services involved

Start here

Recognise this problem in your own org?

Send us the details. We will tell you whether it is a configuration fix, an architecture problem, or something you can solve without us.

Get a proposalEmail us directly

24/7 support — response within one business hour