This document provides guidance on key considerations for implementing partner communities in Salesforce. It recommends having a clear vision for how the partner community will work and engaging internal teams early. It also stresses the importance of building an integrated, intuitive experience for partners that considers branding, legal, and other business implications. Additionally, it suggests reviewing security models thoroughly and testing integrations with other systems. Finally, it advises having a solid rollout strategy that involves user acceptance testing and getting feedback from select partners.

1. Keys Things to Consider When
Implementing Partner
Communities
Viet Nguyen
Lead Salesforce Consultant
@its_viet
​ Jayvin Arora
​ Philadelphia Salesforce User Group Leader
​ @JayvinArora

2. ​ Safe harbor statement under the Private Securities Litigation Reform Act of 1995:
​ This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties
materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results
expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed
forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items
and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning
new, planned, or upgraded services or technology developments and customer contracts or use of our services.
​ The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new
functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our
operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any
litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our
relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our
service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger
enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our
annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter.
These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section
of our Web site.
​ Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently
available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based
upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking
statements.
Safe Harbor

3. Viet Nguyen
Lead Salesforce Consultant, Traction on Demand
@its_viet

4. Jayvin Arora
Salesforce Technical Lead, Soliant Consulting
Salesforce MVP

5. Audience
You are looking to roll out Partner Communities.
You have been asked to roll out a Partner Community.
You are involved in a Partner Community implementation.

6. Keep in mind about Partner Communities…
They are EXTERNAL facing
systems that you can build as
an admin, that touch
customers!

7. Introduction
• Connects you with your Partners
• Different from User Communities
• Common use cases:
§ Collaborate on pipeline
§ Provide Support
§ Share Content & Data with Partners
• Easy, seamless access
• One system for internal teams

8. 1. Have a clear vision
• Identify processes involving Partners
• Understand & document current state
• Identify efficiencies in the new Partner process

9. 1. Have a clear vision
• Review the common use cases for Partner Communities
• Engage with internal teams early: Sales, Marketing, Legal,
Support, Delivery etc.
• Think about Partner adoption

10. 2. Build an integrated, intuitive experience!
• Treat it as a customer facing website
• Consider branding, legal, sales, marketing, delivery implications
• Communities: flexible out of the box
• Standard Salesforce best practice apply: go native!
• Work with Marketing for branding guidelines

11. 2. Consider Branding Guidelines

12. 2. Consider Branding Guidelines

13. 3. Consider Integrations
• What other data could be helpful for Partners?
• Enhance data access for Partners

14. 3. Consider Integrations
• From your CMS, ERP, Internal databases
• Use APIs, Web Services, Lightning Connect

15. 4. Review your security model
• Org Wide Defaults
• Ensure proper access on Profiles
• Use field level security
• Review List views, Reports folders
• Review Workflows, validation rules, triggers
Test, test and test!

16. 4. Review your security model

17. 4. Review your security model

18. 5. Have a solid roll out strategy
• UAT with internal teams
• Select a team of Beta Partners
• Use Partners you have close relationships with
• Use different types of Partners
• Provide guidelines, facilitate feedback process
• Emphasize advantages for Partners

19. Summary
1. Have a vision
2. Build an integrated, intuitive experience!
3. Consider Integrations
4. Review your security model
5. Have a solid roll out strategy
They are EXTERNAL facing
systems that you can build as an
admin, that touch customers!

20. Keep the learning going in the Admin Lodge
Admin Theater
55+ Sessions by Admins for Admins!
Visit Customer-Led Demos Learn more with Trailhead!
Earn your UI Customization badge

21. Q&A

22. Thank you