TPRM vs. SLO Portals
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello All,
I'm curious who has Third-party Risk Management (TPRM) and Supplier Lifecycle Operations (SLO) installed. Have do Third-parties come in to your instance, Do they use one portal for both or the module related portals?
Any information is helpful? Curious as Both contain specific information for the module, yet overlap in some places.
Thanks.
M.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
Hello @MehernoshA ,
They are separate portals by default, each serving a distinct purpose:
- TPRM (Vendor Portal) — used by third parties to complete risk assessments and questionnaires.
- SLO (Supplier Portal) — used by suppliers for onboarding, contract, and operational tasks.
One Portal or Two?
In real time, there could be 3 possible ways
Option 1 — Most common is to leverage as Separate Portals
Each module has its own portal with purpose-built UI. Third parties access the Vendor Portal for risk tasks and the Supplier Portal for operational tasks. This keeps the UX clean but requires third parties to use two different entry points.
Option 2 — Unified Experience via Service Portal / ESC
Some organizations build a custom landing page or use Employee Service Center (ESC) as a single entry point that links out to both portals, giving third parties one URL with directed navigation.
Option 3 — Role-Based Routing
If a third party is both a supplier (SLO) and a vendor under risk assessment (TPRM), their user role determines which portal surfaces relevant tasks — sometimes combined with a unified portal approach.
References:
Thanks,
Vinod Kumar M