Ignyto builds Salesforce Experience Cloud portals for customers, partners, distributors and residents across the UK and Ireland — with the sharing model, licensing and security thought through before the first page is designed. When it works, customers and partners answer their own questions at midnight, and your team stops being the search interface for your own data.
Who sees which record, decided and tested first. This is where portal projects fail, and it is not a design question.
External identity, customer community and partner community licences modelled against real user numbers before you commit.
Case submission, order and job status, document access and knowledge — the calls your team currently takes by phone.
Lead and opportunity management for indirect channels, with budget and performance visibility for your channel managers.
Branded pages and custom Lightning components where the standard set does not go far enough.
Guest user profiles restricted properly — an audited default rather than an open door.
Portal projects fail here, not in design. This is the diagram we agree with you in week one.
Locked down to published content only. No object access unless explicitly granted, and audited.
Login and profile. Cheapest licence, suitable when a user only needs their own records.
Cases, orders, documents and knowledge — their own account only, enforced by sharing sets.
Leads, opportunities and performance for their own territory. The expensive one, so modelled first.
Ignyto builds a test matrix of every user type against every object and record type, and walks it with you. It is unglamorous and it is why the portals we build do not leak data between accounts.
A portal is worth building when it removes work from your team or revenue friction from your channel. Ignyto scopes it against both, and against the licence cost it carries.
Status, documents and case history available without anyone picking up the phone.
Distributor pipeline and performance in one place, so partnerships are managed on evidence.
The right licence type chosen up front, which is usually the largest single cost in a portal programme.
“Ignyto were recommended by Salesforce to us and we have been delighted by their advice, their professionalism and their service. We will continue to partner with Ignyto for our Partner Engagement solution.”
“Ignyto were outstanding in building our distributor portal from scratch, while learning the nuances of our business model.”
No pitch deck. We will tell you what the work involves, roughly what it costs, and whether the return is there.
Ignyto builds customer self-service portals, partner and distributor portals, and resident or member portals on Salesforce Experience Cloud, including case submission, order status, document access and knowledge.
It depends on user numbers and what they need to do. Ignyto models external identity, customer community and partner community licences against your real usage before you commit, because licensing is usually the largest cost in a portal programme.
Almost always the sharing and security model. Ignyto designs and tests who can see which record before any page is designed.
Self-service agents in a portal are the fastest route to deflection, and the fastest route to a wrong answer in front of a customer. Ignyto runs a fixed-scope AI readiness assessment that establishes what an agent could truthfully answer from your Salesforce today, shortlists the use cases worth doing, sets the guardrails, and hands you a costed plan. Fixed scope, no obligation to build with us.
Start with the sharing model and the licence maths. We will tell you what the portal costs to run before you commit to building it.