Start with the workflow, not a product badge
A Salesforce implementation might support service, sales, quoting or another business process. State who needed to do what and where the existing workflow failed. Then explain whether configuration, Flow, Apex, an integration or a change in process addressed the need.
Agentforce work can involve a defined task, instructions, grounded data and permitted actions. A professional should be able to describe the human handoff and what happens when the agent lacks enough information. Do not mistake trying a demonstration for implementing and operating a governed workflow.
- Explain the real task and the authorized data the solution could use.
- Describe what was tested and what happened when the answer or action was uncertain.
- Separate your contribution from configuration supplied by a platform or a wider team.
Make Data Cloud experience specific
Data Cloud-related work may involve connecting sources, understanding identities and making information useful for a defined purpose. Good descriptions identify the data owners, the quality assumptions and the access boundaries. Simply naming a data product does not show how a customer or team could use it safely.
Where a process reaches another system, integration contracts and errors matter. MuleSoft experience, for example, could mean building APIs, orchestrating connectivity or consuming an existing integration. Distinguish these roles. If you worked with Revenue Cloud, explain the particular quoting or revenue workflow rather than implying universal product expertise.
- Name the sources or systems in non-confidential terms.
- Describe how a failed or duplicated update was noticed and handled.
- Explain which permissions or approvals were relevant to your part of the work.
Explain what you built and how you kept it safe
Platform changes affect people who use an org every day. Explain how a change was reviewed, deployed and explained to those users. Include how you validated behavior after release and how the team could reverse or adjust a change if needed.
Certifications can be useful context when accurately stated, but this guide is not a certification checklist. A specific example of a maintained workflow or investigated failure says more about your responsibilities than a list of Salesforce product names.
Describe a real Salesforce project in your profile
Describe one process, your exact responsibility and the Salesforce capabilities involved. Show a trade-off—configuration versus custom code, or data freshness versus operational complexity—and how you checked the result. Remove client identifiers and private org details before sharing an example.
Update the entry as your experience changes. If Agentforce or Data Cloud is new to your work, call it exploration until you can describe an implemented responsibility. That distinction supports a better conversation with an organization considering your profile.
Turn this guide into your profile
- Create an account and verify your email.
- Complete your profile; you can optionally upload a .pdf or .docx resume during setup, and manage resumes later in your Talent Passport.
- Keep your Talent Passport current as your work changes.