Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Setting up a Partner Community is 99% permissions and 1% prettiness. 

Steps

See some of the posts mentioned below for some steps to set up a community

Use the setup steps noted in EDL Consulting Blog » 7 Steps to Set Up a Basic Salesforce Community

My Steps

  • Create the URL
  • Create the Community
  • Set the levels of Profiles
  • Set the Profiles that can use the Community
  • Choose a theme (I probably would not be building a community like this). 
  • Set the Tabs visible in the Community

Notes

  • Your users are going to be annoyed at the black bar. There is no way around this! 
  • Everything you do for your partners should be visible by the internal users, so they will need to know about this and know that there is new data (eg Accounts, Contacts) that they didn't create and they don't own. 

Suggestions

  • Create the Alias for the users as ABC-joebloggs - ABC being the company name of the user. 

Gotchas an things to remember

Users

Use the Domain or Community unique logins as noted above in Carving in the Clouds: Recommended Usernames for Salesforce Communities. 

Set the Alias to have the Partner Company in the name so it's easily visible. 

Fields

You want your partner specific fields to be visible by partner users and internal users, but internal fields only visible to internal users. Try not to mix them up on Page Layouts, or create a specific section for Partner Content on the Page Layout. 

Make a note on the Description field if that field is used for Partners - for auditing purposes. . 

Maven's mate sample field block with the Description field shown. 

    <fields>
        <fullName>PartnerField__c</fullName>
        <description>Partners Only</description>
        <externalId>false</externalId>
        <inlineHelpText>The Help Text for this Partner Field.</inlineHelpText>
        <label>Partner Field</label>
        <length>255</length>
        <required>false</required>
        <trackFeedHistory>false</trackFeedHistory>
        <trackHistory>false</trackHistory>
        <type>Text</type>
        <unique>false</unique>
    </fields>

List Views

Ensure all existing List Views are visible only to Internal Users now. 

Maven's Mate sample view block with visibility settings. 

    <listViews>
        <fullName>RecordTypeA_Accounts</fullName>
        <columns>ACCOUNT.RECORDTYPE</columns>
        <columns>ACCOUNT.ACCOUNT_NUMBER</columns>
        <columns>ACCOUNT.NAME</columns>
        <columns>ACCOUNT.ADDRESS1_STATE</columns>
        <columns>ACCOUNT.ADDRESS1_COUNTRY</columns>
        <columns>ACCOUNT.PHONE1</columns>
        <columns>CORE.USERS.ALIAS</columns>
        <filterScope>Everything</filterScope>
        <filters>
            <field>ACCOUNT.RECORDTYPE</field>
            <operation>equals</operation>
            <value>MyRecordType</value>
        </filters>
        <label>Record Type A Accounts</label>
        <sharedTo>
            <allInternalUsers></allInternalUsers>
        </sharedTo>
    </listViews>


 

 

  • No labels