Skip to main content

Return to TX Community

Liaison

Managing Community Users

  1. Last updated
  2. Save as PDF

Provisioning Community Users Manually

Step 1: Add the Enable Customer User button to your Contact layout

  1. Navigate to Setup and search for Contacts
  2. Select the Contact object and navigate to Page Layouts.
  3. Select the Buttons group from the page layout palette and then drag the Enable Customer User button onto the page layout.
  4. Save your changes.

 Step 2: Enable Customer User 

  1. Navigate to the user’s Contact record.
  2. From the Manage External User picklist, select Enable Customer User and then select Go.
  3. You will be taken to a New User page with the Contact’s information defaulted.
  4. Select the appropriate User License and Profile.
  5. Make sure an Email has been specified.

Associating a Contact to a Related User

The Related User field (TargetX_Base__Related_User__c) enables you to associate a Contact record with a User record.

Note: Associating a Contact with a Related User does NOT enable the Community User.  For details on enabling Community Users, see: How to Manually Provision Community User.

  1. Update the Contact Layout to include the Related User field:
    1. Navigate to Setup and search for Object Manager.
    2. Locate the Contact (Student) object.
    3. Click on Page Layouts.
    4. Select the Contact Layout.
    5. From the Page Layout palette, select Fields.
    6. Drag the Related User field into the layout.
    7. From the Page Layout palette, select Mobile & Lightning Actions.
    8. Drag the Log in to Community as User into the Salesforce Mobile and Lightning Experience Actions section.
    9. Save your changes.
  2. Navigate to the Contact (Student) tab.
    1. Select a record where you want to associate a User.
    2. Navigate to the Details tab.
    3. Edit the Related User field.
    4. Search for the appropriate User.
    5. Save your changes.

Note: Ensure your Community has the User's Profile selected under Community Workspaces: Administration > Members (Selected Profiles).

You can now use the Log in to Experience as User action to navigate to your Community as the selected Contact:

Log in to Experience as User option

Deactivating Community Users

  1. Community users should be deactivated by navigating to the Contact Record.
  2. Click Manage External User.
  3. Select Disable Customer User.

Disable Customer User menu option

Note: TargetX has a Synchronization Task in Informatica that can run on a schedule to clean up users that should be deactivated. You can submit a Support ticket to get the Informatica tasks added to your system. If you are a Premier client, you can open a Configuration ticket.

If you want to mass disable Community users, see the Salesforce Help & Training article: Mass disable portal users with Data Loader.

Preventing Community Users from changing their Mailing Address

You can use CSS code to hide the Profile page from Community Users and prevent them from changing their Email Address OR you can edit the Visualforce Page to remove 'mailing address' information:

Option 1: Update the Community Theme record 

DISCLAIMER: This CSS tag is not supported or maintained by TargetX and is meant as an example of how you may choose to use CSS within our products. Some or all of the customizations these tags provide may change or no longer apply to your instance at any time. If the CSS impedes expected functionality in the TargetX product at any time, we recommend you remove the CSS to regain functionality.  


You can use CSS code to hide the 'Profile' page from Community Users:

  1. Navigate to the Community Theme tab and select the appropriate record.
  2. Select Edit.
  3. Add the following to the CSS field to hide 'My Profile':
#navbar > ul > li:nth-child(1) > a{
display: none;
}

Option 2: Edit the TX_MyProfilePage VF page  

You can edit the TX_MyProfilePage VF page to hide the mailing address info from the profile page and prevent community users from changing it:

  1. Navigate to Setup and search for Visualforce Pages.
  2. Locate TX_MyProfilePage and select Edit.
  3. Comment out the following sections by adding <!-- at the beginning of the code block, then --> at the end of the block, as shown below:
<!-- <apex:pageBlockSection id="editAddressInformation" columns="1" title="{!$Label.site.address_information}">
<apex:inputField styleClass="form-control style_2" id="editstreet" value="{!user.street}"/> 
<apex:inputField styleClass="form-control style_2" id="editcity" value="{!user.city}"/> 
<apex:inputField styleClass="form-control style_2" id="editstate" value="{!user.state}"/> 
<apex:inputField styleClass="form-control style_2" id="editpostalcode" value="{!user.postalcode}"/> 
<apex:inputField styleClass="form-control style_2" id="editcountry" value="{!user.country}"/> 
</apex:pageBlockSection> -->
AND
<!--  <apex:outputField id="detailstreet" value="{!user.street}"/>
<apex:outputField id="detailcity" value="{!user.city}"/>
<apex:outputField id="detailstate" value="{!user.state}"/>
<apex:outputField id="detailpostalcode" value="{!user.postalcode}"/>
<apex:outputField id="detailcountry" value="{!user.country}"/>  -->
  1. Save your changes.

Validating permissions for a Community User

Since Community Users don’t log in to the TargetX CRM directly, you’ll need to take some additional steps before validating permissions for this type of user.

Step 1: Temporarily remove the 'Page Stopper'

  1. Navigate to Setup and search for Digital Experiences (formerly All Communities).
  2. Select the Community where you want to validate permissions.
  3. Select  Manage > Administration > Branding.
  4. Remove TXStandardPageStopper from the Header Field.
  5. Remove TXStandardPageStopper from the Footer Field.
  6. Save your changes.
  7. Run Permission Scanner (see Step 2).

For more information on the TargetX Page Stopper, see Setting up Security for your Community.

Step 2: Login as Community User

  1. Navigate to Profiles and click on the Name for the Community User profile you want to validate.
  2. In the "Enabled Visualforce Page Access" section, validate that the following page is listed:
    1. TX_Permissions.permissionScanner
  3. In the 'Enabled Apex Class Access" section, validate that the following Apex Class is listed:
    1. TX_Permissions.permissionChecker
  4. Log into the Community as a 'Community User' (using the profile you validated in #1).
  5. Edit the URL by removing the homepage and adding the following at the end:
    1. TX_permissions__permissionScanner

For example:
https://targetxdemo-1234.force.com/OnlineApp/TargetX_App__OnlineAppHome

Would change to:

https://targetxdemo-1234.force.com/OnlineApp/TX_permissions__permissionScanner

  1. Select the Enter key.

Permission selection window

  1. Select the Product/Feature and the Version.
  2. Select  Validate Permissions for <User Name>.

Step 3: Replace the 'Page Stopper'

  1. Navigate to Setup and search for Digital Experiences (formerly All Communities).
  2. Select the Community where you want to validate permissions.
  3. Select  Manage > Administration > Branding.
  4. Paste the following value into the Header field: TXStandardPageStopper 
  5. Paste the following value into the Footer field: TXStandardPageStopper 
  6. Save your changes.


 

Validating permissions for a Site User

Since Site Users don’t log in, you’ll need to take some additional steps before validating permissions for this type of user.

Note: If the Site Permissions you are validating is for a Community (i.e., Online Application or Portal) - you will need to remove the Page Stopper temporarily, complete the steps below, and then ADD the Page Stopper back. Please see steps 1 and 3 in the article Validating permissions for a Community User.

  1. Navigate to Setup and search for Sites.
  2. Click the Site Label for the Site you want to validate.
  3. Select Public Access Settings.
  4. In the Visualforce Page Access section, validate that the following page is listed:
    1. TX_Permissions.permissionScanner
  5. In the Apex Class Access section, validate that the following Apex Class is listed:
    1. TX_Permissions.permissionChecker

Note: If the Apex Class above is not listed, you can proceed to the next step.

  1. Navigate back to your Site and copy the Site URL into an incognito or private window.
  2. Edit the URL by removing the homepage and adding the following at the end:
    1. TX_permissions__permissionScanner


For example:

https://targetxdemo-1234.force.com/OnlineApp/TargetX_App__OnlineAppHome

Would change to:

https://targetxdemo-1234.force.com/OnlineApp/TX_permissions__permissionScanner

  1. Select the Enter key.

Permission selection window

  1. Select the Product/Feature and the Version.
  2. Select  Validate Permissions for <Site Name> Site Guest User.

 

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Page type
    Topic
    Content Reuse
    Reused Content
  2. Tags
    This page has no tags.