01 Getting Started

This tutorial covers setting up an encrypted on top of the SmartV process.

This ensures your user is authenticated and is authorized to certain parts of your project.

This will be achieved by passing an Encrypted ID on the page URL and comparing it to the logged-in record encrypted ID.

Refer to the Record ID encryption process in the following tutorial.

02 Creating Variables

To pass the allowed encrypted Id on the page URL create a custom variable.

1. Select the project settings gear icon.
2. Select the Tools tab and click the Custom Variables gear icon.

3. Click on the Static tab and add a new custom variable. For this example, we named the variable enc_id.
4. Select the Kebab menu and enable the Map to URL checkbox. Click Apply.
custom variables - static variable

03 Setting a SmartV Parameter

1. Select the project settings gear icon.
2. Select the User Access tab and click the SmartV gear icon.
project settings > user access tab
3. Navigate to the Parameters step and create a New Parameter. Give your parameter a name and choose the corresponding Salesforce field using the dropdown.
configure smartv login parameters step

04 Configuring a Page Load Every Time Action

1. Expand the pages menu and click the kebab menu next to the home page.
2. Click the Configure Actions button from the submenu.

3. Select the Every Time tab and click the Start + icon.
configure every time action
4. Choose Condition and click Next.
choose condition node
5. Configure the following condition: if the encrypted id does not equal the SmartV encrypted id. Click Next.
configuring condition
6. Add a Tag and click Insert.
7. Click the Then + icon and choose Affected Element. Click Next.
choose affected element node

8. Select the elements you wish to secure- you can choose to hide or replace these elements for non-authorized users. We recommend to add a text or message notifying the user he is not authorized to review this data.

Click Next.

configuring affected element

9. Add a Tag, click Insert, and click Apply.

While testing via Preview- map the authorized encrypted record ID to the project URL.

If the logged-in record id doesn't match the URL one, the secured data should be hidden/replaced, as was set-up on the project.

05 Got Feedback?

Additional Resources