Salesforce Experience Cloud's main use case for us is building secure customer and partner portals that enable self-service and improve collaboration. We use it to allow customers to create and track support cases, access knowledge articles, manage their profiles, and interact with our support team. On the partner side, it helps users access shared records, collaborate on opportunities, and securely exchange business information. My role involves customizing the portal using Experience Builder, Lightning Web Components, Apex, and Flows.
My main use case for Salesforce Experience Cloud is that I have used Health Cloud and Nonprofit Cloud for major medical companies and NGOs. When I open Salesforce Experience Cloud daily, I function as both a Salesforce admin and developer, so depending on the stories and current requirements, I do what is needed. Typically, the first thing I access when working in Salesforce Experience Cloud as an admin developer is the setup tab.
There were a couple of different use cases for Salesforce Experience Cloud. One was working for a portal for end users wherein they would see the data of their associated partners and could create forms, submit details, send claims, reimbursements, and so on. This was within the healthcare industry. The other one was within the real estate industry, and that was for the partners, not the end customers, to view their details such as successfully converted deals, commission calculations, and how those communications were processed.
Salesforce Associate Architect at a tech services company with 51-200 employees
Real User
Top 10
Oct 7, 2024
We implemented a maintenance app for contractors. Within the Experience Cloud portal, contractors could log in, raise work orders for maintenance requests, and manage those tasks through the portal. Internal users can see specific actions based on criteria such as a request's status.
We are currently working on an Experience Cloud site. It is one site that you can create using Salesforce. It is a normal site where users can log in using their credentials. Their users, such as customers or partners, can process something on their own. It is independent of complete Salesforce. While the database is linked to Salesforce CRM, it remains an independent site with an independent URL. The URL can be changed, and it can be used anywhere. Any support team can use it, for instance. They can log into the site, enter the credentials, and perform some process or request. Those actions can be done using Experience Cloud.
Find out what your peers are saying about Salesforce, Agentcis, Channeltivity and others in Partner Relationship Management (PRM). Updated: August 2026.
Partner Relationship Management solutions enhance collaboration between companies and their partners, streamlining communication, training, and business processes through centralized platforms.PRM software offers comprehensive tools for managing partner relationships. These platforms function as a bridge between organizations and their network, supporting tasks like partner onboarding, training, and performance tracking. By providing partners with access to resources, guidance, and insights,...
Salesforce Experience Cloud's main use case for us is building secure customer and partner portals that enable self-service and improve collaboration. We use it to allow customers to create and track support cases, access knowledge articles, manage their profiles, and interact with our support team. On the partner side, it helps users access shared records, collaborate on opportunities, and securely exchange business information. My role involves customizing the portal using Experience Builder, Lightning Web Components, Apex, and Flows.
My main use case for Salesforce Experience Cloud is that I have used Health Cloud and Nonprofit Cloud for major medical companies and NGOs. When I open Salesforce Experience Cloud daily, I function as both a Salesforce admin and developer, so depending on the stories and current requirements, I do what is needed. Typically, the first thing I access when working in Salesforce Experience Cloud as an admin developer is the setup tab.
There were a couple of different use cases for Salesforce Experience Cloud. One was working for a portal for end users wherein they would see the data of their associated partners and could create forms, submit details, send claims, reimbursements, and so on. This was within the healthcare industry. The other one was within the real estate industry, and that was for the partners, not the end customers, to view their details such as successfully converted deals, commission calculations, and how those communications were processed.
We implemented a maintenance app for contractors. Within the Experience Cloud portal, contractors could log in, raise work orders for maintenance requests, and manage those tasks through the portal. Internal users can see specific actions based on criteria such as a request's status.
We are currently working on an Experience Cloud site. It is one site that you can create using Salesforce. It is a normal site where users can log in using their credentials. Their users, such as customers or partners, can process something on their own. It is independent of complete Salesforce. While the database is linked to Salesforce CRM, it remains an independent site with an independent URL. The URL can be changed, and it can be used anywhere. Any support team can use it, for instance. They can log into the site, enter the credentials, and perform some process or request. Those actions can be done using Experience Cloud.