Enabling the Egnyte Integration

Please note: This content is intended for Practifi System Administrators and is technical in nature. The steps described in this article may not be able to be completed without System Administrator permissions. Please discuss your integration installation plans with your Practifi Customer Support Team for their assistance.

Overview

Egnyte is a cloud-based file management and collaboration platform that enables organizations to store, organize, and share files securely across teams and clients. By integrating Egnyte with Practifi, your advisory firm can manage client documents, compliance records, and planning materials directly from the Practifi platform without switching between the systems. This integration creates a seamless experience where advisors can access a Shared Directory structure organized by client records within Practifi, reducing friction in the advisor workflow and improving document governance.

The Egnyte integration connects to Practifi through a managed package installed from Salesforce AppExchange. The integration creates custom objects and Visualforce pages that allow administrators and advisors to configure folder structures, set file access permissions, and link records. Unlike integrations managed by Practifi Customer Success Engineering, the Egnyte integration is entirely self-service: you install the managed package, complete the configuration steps, and enable the feature for your team.

This guide explains how to install the managed package, configure permissions, connect your Egnyte domain, add the Egnyte Canvas to record pages, and test the integration end-to-end. By the end of these steps, your advisors will be able to access Egnyte files directly from Client and Prospect records in Practifi.

• Overview
• Prerequisites
• Understanding the Integration Architecture
• Planning Your Installation
• Installing the Managed Package
• Configuring Permission Sets
• Connecting Your Egnyte Domain
• Configuring Remote Site Settings
• Practifi-Specific Setup
• Configuring Folder Templates
• Testing and Verification
• Troubleshooting
• Security Considerations
• Known Limitations
• Frequently Asked Questions

---

Prerequisites

Before installing the Egnyte managed package, verify that your Salesforce org and Egnyte account meet the following requirements. Failing to meet any of these prerequisites may cause the installation to fail or prevent the integration from functioning correctly.

• Practifi / Salesforce System Administrator access
• Salesforce Group, Enterprise, or Unlimited edition
• Egnyte subscription with Salesforce Integration licenses purchased for employee users
• Egnyte Administrator account with Egnyte or AD authentication (not SSO)
• Two-Factor Authentication (TFA) must be temporarily disabled on the Egnyte Administrator account during setup

---

Understanding the Integration Architecture

Core Objects Used

The Egnyte for Salesforce managed package is a complete integration solution published by Egnyte, Inc. on the Salesforce AppExchange. Egnyte for Salesforce does not create custom Salesforce objects or sync data to Practifi records. Instead, it provides file storage functionality linked to existing records.

Component	Type	Description
Egnyte Sync Configurations	Custom Object	Stores sync configuration settings
Egnyte Folder Templates	Custom Object	Defines folder/sub-folder templates for new records
Egnyte Folder Paths	Custom Object	Tracks folder path associations with Salesforce records
Egnyte Sync Queue	Custom Object	Manages sync queue for file operations

Supported Salesforce Objects

Any custom Salesforce object can be configured for the Egnyte for Salesforce integration. The following standard objects can be integrated with Egnyte:

• Leads
• Cases
• Accounts
• Contacts
• Opportunities
• Campaigns

File Hierarchy and Data Flow

The Egnyte integration organizes files using a hierarchical folder structure within Egnyte’s Shared Directory. When an advisor links a record in Practifi (such as a Client or Prospect), the integration automatically creates a corresponding folder structure in Egnyte following this pattern:

Shared Directory → Salesforce.com → [Object Type] → [Individual Record]

For example, if you link a Client record with the name “Acme Corp,” the integration will create folders in Egnyte like this:

Shared Directory → Salesforce.com → Clients → Acme Corp

Files placed in this folder are then accessible to advisors directly from the Practifi Household page. When a Prospect record is converted to a Client record in Practifi, the files associated with that Prospect automatically follow the record to the Client folder structure, ensuring no documents are lost during the conversion. 

The data flow between Practifi and Egnyte through this integration is bidirectional. File content is accessible from both platforms. Content added at the record level in Practifi becomes available in Egnyte, and content added through Egnyte appears at the record level in Practifi.

---

Planning Your Installation

Before installing the managed package, decide whether to install in a sandbox first or proceed directly to production. A sandbox allows you to test the entire configuration process without affecting live users. If you have a sandbox available, we recommend installing it there first to familiarize yourself with the setup steps.

When installing the package in a sandbox environment, you can use a trial Egnyte domain, which is set up from the Egnyte Domain Configuration page. The trial domain comes with five pre-configured integration licenses. Contact your Egnyte contact to request additional licenses or to convert the trial Egnyte domain beyond the 14-day trial period.

---

Installing the Managed Package

1. Navigate to the Salesforce AppExchange and search for “Egnyte for Salesforce.” The official package is published by Egnyte, Inc.
2. Find the package with the following details:
   1. Name: Egnyte for Salesforce
   2. Publisher: Egnyte, Inc.
   3. Package ID: a0N30000000q2LaEAI
      
3. On the AppExchange page, click the Get It Now button. You will be prompted to log in to your Practifi org if you are not already logged in. We recommend installing this package in a sandbox environment first before installing it in a production environment.
   
4. Select Install for All Users to ensure all users have the required permissions. All users do not need to be licensed Egnyte users, but this setting ensures all users have enough permissions for the app to work as users create and modify records in your Practifi organization.
5. Click Install to complete the installation process.
6. Once you receive the installation confirmation email, log in to Salesforce and verify that the package components are present:
   1. Go to Setup → Installed Packages. 
   2. Search for “Egnyte” and verify that the package appears in the list with a status of “Installed.”
      

Upgrading Notes

Version 3.x and 2.x are independent of version 1.x. If your firm is using a 1.x version of the Egnyte integration, install the latest version before uninstalling 1.x. Egnyte recommends uninstalling or disabling 1.x after verifying that the latest version is working in your organization. To upgrade, open the AppExchange listing and select Get It Now.
 

---

Configuring Permission Sets

The managed package includes a pre-built permission set named “Egnyte User” that grants all necessary permissions for accessing Egnyte integration features.

1. Go to Setup → Permission Sets.
   
2. Click on the Egnyte User permission set.
   
    
3. Review the list of permissions to familiarize yourself with what this permission set grants access to. You do not need to make changes; the permissions are pre-configured by the managed package.
4. Click Manage Assignments next to the Egnyte User permission set.
   
5. Search for and select the users or groups who should have access to Egnyte. Typically, this includes advisors, support staff, and compliance personnel. Select the checkbox next to their name or select the checkbox at the top of the checkbox column to select all users.
   
6. Click Add Assignment. The selected users now have access to Egnyte integration features.
   

You can assign the permission set to multiple users at once. Changes take effect immediately. Users do not need to log out and log back in.

Profile Access

Each profile your firm uses will need its Egnyte connected app access confirmed to use the integration. To confirm this:

1. Go to Setup → Profiles.
   
2. Locate the profiles that your firm uses, typically Practifi User - Salesforce, Practifi User - Salesforce Platform, and System Administrator. Select one profile name.
3. Select Assigned Connected Apps. 
   
4. Ensure that Engyte for Salesforce is listed under Assigned Connected Apps. If it is not listed:
   1. Click Edit.
   2. Select Engyte for Salesforce under the Installed Connected Apps list. 
   3. Use the Add button to move Egnyte for Salesforce to the Enabled Connected Apps list.
   4. Click Save.
      
5. Repeat these steps as needed to confirm app access is enabled for the needed profiles in your organization. 

If your firm uses custom profiles, edit each profile to have at least the following Custom Object Permissions:

• Engyte Sync Configurations - View All
• Egnyte Folder Templates - View All
• Engyte Folder Paths - View All
• Egnyte Sync Queue - Modify All, Create

---

Connecting Your Egnyte Domain

The next step is to authorize your Egnyte domain and complete the OAuth flow. This establishes a secure connection between Salesforce and Egnyte.

Please note: While the Egnyte integration can work within Salesforce Lightning and Practifi, these configuration steps must be done in Salesforce Classic. 

1. Select your user icon in the upper-right corner and click Switch to Salesforce Classic.
   
2. Click the + option in the upper-left corner. 
   
3. Locate and click the Egnyte Domain Configuration tab option.
   
4. If you do not have an Egnyte Domain, click the Egnyte Trial Domain button to create a trial domain first. 
5. If you already have an active Egnyte domain:
   1. Click Edit in the Egnyte Domain Configuration section.
   2. Enter your Egnyte domain name in the Egnyte Domain field.
   3. Use the complete address without the http:// or https:// (e.g., acme.egnyte.com).
   4. Leave all other settings at their default value.
   5. Click Save. 
6. A login screen for your Egnyte domain will appear. Sign in using administrator credentials. The administrator account must use Egnyte or AD authentication, and two-factor authentication must be disabled temporarily. 
7. After successful authentication, click Continue to complete the setup. If a "page not found" error displays, it may be due to browser caching. Try using an Incognito window or a different browser, like Firefox or Safari, to fix this error.
8. Copy the URL domain from the browser window and save it somewhere easily accessible, as it will be needed for configuring Remote Site Settings. The URL begins with http://efs. You will need to copy only the domain portion and not the full URL. This URL can only be copied when in Salesforce Classic.

Please note: If the OAuth flow fails, verify that your Egnyte admin account is using password authentication and that two-factor authentication is temporarily disabled. SSO accounts and 2FA-protected accounts may not be able to complete the OAuth flow. After the initial authorization, you can re-enable 2FA on your admin account.

---

Configuring Remote Site Settings

Remote Site Settings allow Salesforce to make outbound calls to Egnyte. Two remote sites will need to be made for this integration. To create these:

1. Go to Setup → Remote Site Settings.
   
2. If remote site entries for Egnyte are not already present, click New Remote Site to create them. You will need to create two entries:

Remote Site Entry 1:

• Remote Site Name: EgnytePackage
• Remote Site URL: The URL copied from before.
• Disable Protocol Security: Unchecked (leave this unchecked for security)
• Active: Checked
  

Remote Site Entry 2:

• Remote Site Name: EgnyteDomain
• Remote Site URL: Your Egnyte domain URL (e.g., https://acme.egnyte.com)
• Disable Protocol Security: Unchecked
• Active: Checked
  

3. Click Save after creating each entry.
4. Go back to Remote Site Settings and verify that both entries are present and show a status of “Active.”

Test the Connection

To ensure the connection to Egnyte is working properly:

1. Use the App Launcher in the upper-left corner to search for and select My Egnyte.
   
2. Verify the Egnyte interface loads successfully.
   
3. If the interface loads successfully, proceed with the installation steps.

---

Practifi-Specific Setup

Now that the integration is authorized and configured, you can add the Egnyte Canvas to Client and Prospect record pages so that advisors can see Egnyte files directly in Practifi. Before configuring Egnyte in Practifi, ensure the Egnyte integration is enabled and configured as outlined in the above steps. 

Adding the Egnyte Tile on Client Record Pages

1. Log in to Practifi and navigate to a Client Record page in your organization. 
2. Click the Setup gear in the upper-right corner and then select Edit Page from the drop-down menu.
   
3. In the left side search bar, search for the "Practifi - Navigation Section" component.
   
4. Drag and drop the component over the Activities' Navigation Section. 
   
5. Configure the new Navigation Section to have the following settings:
   • Title: Egnyte
   • Icon: fas fa-star-of-life
     
6. Drag and drop the Egnyte component below the Egnyte Navigation Section you just added to the page.
   
7. Click Save. This will clone the Client Record Page. 
   
8. A pop-up window will appear to activate the new page. Click Activate.
9. Assign the page to the required Apps:
   • Advisor
   • Client Service
   • Marketing
   • Management
   • Settings
10. Click Next.
11. Select the form factor, which is Desktop by default, and click Next.
12. Select the following Record Types:
    1. Household Client
    2. Individual Client
    3. Organization Client
13. Click Next.
14. Select the Profiles that need to access this page and then click Next.
15. Review the Assignments and click Save.
    

Adding the Egnyte Tile on Prospect Record Pages

1. Log in to Practifi and navigate to a Prospect Record page in your organization. 
2. Repeat steps 2 through 11 in the "Adding the Egnyte Tile on Client Record Pages" section above.
3. Select the following Record Types:
   1. Household Prospect
   2. Individual Prospect
   3. Organization Prospect
4. Click Next.
5. Select the Profiles that need to access this page and click Next.
6. Review the Assignments and click Save.

Please note: If you have created multiple Practifi page layouts (e.g., one for advisors and one for back-office staff), you may want to add the Egnyte Canvas to all relevant layouts so that all users can access Egnyte files.

---

Configuring Folder Templates

Folder templates allow you to automatically create a standardized folder structure in Egnyte whenever a new record is linked. This is optional but highly recommended because it ensures consistency and saves time.

Step 1: Plan Your Folder Template Structure

Before creating templates, decide what folders should be automatically created for each record type. Common examples include:

For Client Records:

• Income Documents
• Tax Returns
• Insurance Policies
• Investment Statements
• Estate Planning Documents
• Meeting Notes
• Compliance Records

For Prospect Records:

• Discovery Questionnaire
• Financial Snapshot
• Initial Documents

Step 2: Create Egnyte Folder Template Records

1. Use the App Launcher in the upper-left corner to search for and select Egnyte Domain Configuration.
2. Access the Folder Templates section.
3. Create templates for:
   • Leads
   • Cases
   • Accounts
   • Contacts
   • Opportunities
   • Campaigns
   • Custom objects
4. Define sub-folder structure for each template. 
5. Click Save.
6. Create additional templates as needed for different record types or use cases.

Step 3: Apply Templates When Linking Records

After templates are created, when you link a new record to Egnyte (by clicking the Egnyte Canvas on a record and selecting the option to initialize the folder), the system will offer the option to apply a template. Select the appropriate template to automatically create the standard folder structure.

---

Testing and Verification

Before rolling out the integration to your entire team, test the following scenarios to ensure everything is working correctly.

Test 1: Verify That Egnyte Canvas Appears on Record Pages

1. Log in to Practifi as a user assigned to the Egnyte User permission set.
2. Navigate to a Client record.
3. Verify that the Egnyte Canvas component is visible on the record page (you should see an Egnyte widget or panel).
4. Repeat for Prospect records if you have added Egnyte Canvas to those pages.

Test 2: Initialize an Egnyte Folder for a Test Record

1. On a Client record, click the Egnyte Canvas component.
2. Click the button or option to initialize or link the record to Egnyte.
3. If you have created folder templates, select the appropriate template. Otherwise, the system will create a basic folder structure.
4. The Canvas should now indicate that the folder has been created and is ready for use.

Test 3: Upload a Test File

1. On the same test record, look for an option to upload or link files within the Egnyte Canvas.
2. Upload a test document (e.g., a PDF or image file) to verify that the upload functionality works.
3. The file should appear in both the Egnyte Canvas (within Practifi) and in your Egnyte Shared Directory (when viewed in the Egnyte web application).

Test 4: Verify File Accessibility

1. Log in to your Egnyte account separately and navigate to Shared Directory → Salesforce.com → [Record Type] → [Test Record Name].
2. Verify that the test file you uploaded appears in the correct folder structure in Egnyte.
3. Log back into Practifi and verify that the file is also visible in the Egnyte Canvas on the Practifi record page.

Test 5: Test Permission Isolation (Package v2.6.1+)

If your organization is running package version 2.6.1 or later, the integration supports per-record permission levels (Viewer, Editor, Owner). Test this feature:

1. On a record with Egnyte configured, look for permission settings or access control options in the Egnyte Canvas.
2. Set a test user’s permission level to “Viewer” and verify that they can see files but cannot edit or delete them.
3. Change another user’s permission to “Editor” and verify that they can modify files.

Test 6: Prospect to Client Conversion

1. Create or locate a test Prospect record that has Egnyte initialized and contains at least one test file.
2. Convert the Prospect to a Client using Practifi’s standard conversion workflow.
3. Verify that the converted Client record now displays the Egnyte files and folders from the original Prospect record. The files should automatically follow the record to its new location in the Egnyte hierarchy.

Once all tests pass, the integration is ready for broader team rollout. Communicate to your advisors how to access and use Egnyte within Practifi.

---

Troubleshooting

Egnyte Canvas Does Not Appear on Record Pages

Symptom: After adding the Egnyte Canvas component to a record page layout, it does not appear when viewing records.

Causes:

• The user does not have the Egnyte User permission set assigned.
• The Egnyte Canvas was added to the page layout, but the page has not been saved or published.
• The user’s profile does not have permission to view Visualforce pages.

Solutions:

1. Verify that the test user has the Egnyte User permission set assigned. Go to Setup → Permission Sets → Egnyte User → Manage Assignments and search for the user.
2. If the user was recently added to the permission set, have them log out and log back in to refresh their session.
3. Go to Setup → Profiles and check that the user’s profile has “View All” permission for the Egnyte Visualforce pages. If not, add the pages to the “Enabled Visualforce Page Access” section.
4. Return to the record page layout editor (Setup → Lightning Pages or Setup → Page Layouts) and verify that the Egnyte Canvas component is present and visible. Re-save the page if necessary.

OAuth Authorization Fails

Symptom: When clicking the “Authorize Egnyte” button on the Egnyte Configuration record, you are redirected back to Salesforce without completing the authorization. No status message appears, or an error is displayed.

Causes:

• The Egnyte admin account is using single sign-on (SSO) instead of password authentication.
• Two-factor authentication (2FA) is enabled on the Egnyte admin account.
• The Egnyte admin account does not have sufficient permissions to authorize third-party integrations.
• Network firewall or security appliances are blocking the connection to Egnyte.

Solutions:

1. Temporarily disable 2FA on the Egnyte admin account. In Egnyte Admin Settings, find the user account and disable two-factor authentication. Then retry the OAuth flow.
2. If your organization uses SSO for Egnyte, contact Egnyte Support or your Egnyte account manager. SSO users may need special configuration to complete OAuth authorization. Some organizations use a service account with password authentication instead of SSO for integration purposes.
3. Verify that the user account is an Egnyte administrator with permission to authorize integrations. Check your Egnyte Admin Settings to confirm the user’s role.
4. Work with your IT/Network team to ensure that no firewalls, proxies, or security appliances are blocking connections to Egnyte’s authentication servers.
5. After the initial authorization is complete, you can re-enable 2FA on the admin account.

Remote Site Settings Error When Accessing Egnyte Files

Symptom: An error appears in the Egnyte Canvas saying “Remote site not allowed” or similar.

Causes:

• Remote Site Settings for Egnyte have not been created or are not properly configured.
• The Remote Site URL does not match your actual Egnyte domain name.

Solutions:

1. Go to Setup → Remote Site Settings.
2. Verify that both required entries exist:
   • EgnytePackage → https://api.egnyte.com
   • EgnyteDomain (or your custom name) → https://[yourdomain].egnyte.com
3. If either entry is missing, create it by clicking New Remote Site.
4. After creating or correcting the entries, log out of Salesforce and log back in. Then test accessing Egnyte files again.

Egnyte Configuration Record Shows “Unauthorized” Status

Symptom: The Egnyte Configuration record displays a status of “Unauthorized” or shows that the connection is disconnected.

Causes:

• The OAuth authorization token has expired.
• The Egnyte admin account password was changed after authorization.
• The Egnyte subscription or Salesforce Integration license was removed or deactivated.

Solutions:

1. Click the Authorize Egnyte button again to re-authorize the connection. Complete the OAuth flow as described in the “Connecting Your Egnyte Domain” section above.
2. Verify that your Egnyte subscription is active and that you have sufficient Salesforce Integration licenses allocated. Log in to your Egnyte admin panel and check your subscription status.
3. If the issue persists after re-authorizing, contact Egnyte Support with your Egnyte domain name and Salesforce org ID for further assistance.

Files Are Not Appearing in Egnyte Canvas

Symptom: The Egnyte Canvas appears on the record page, but no files are shown, or it displays “No files” even though files have been uploaded.

Causes:

• The record has not been linked to Egnyte (the folder initialization has not been completed).
• The user does not have permission to view the folder (permission level issue).
• The files are in Egnyte, but in a different folder than the one displayed by the Egnyte Canvas.

Solutions:

1. On the record page, look for an option within the Egnyte Canvas to initialize or link the record. Follow the prompts to create the Egnyte folder structure for this record.
2. After initialization, the Canvas should display the corresponding Egnyte folder and any files within it.
3. If files still do not appear, log into your Egnyte account directly and navigate to Shared Directory → Salesforce.com → [Record Type] → [Record Name] to verify that the folder structure and files exist in Egnyte.
4. If files exist in Egnyte but are not showing in the Canvas, verify that the user has at least “Viewer” permission on the folder (if using package v2.6.1+).

---

Security Considerations

OAuth Token Management

The Egnyte integration uses OAuth 2.0 to authorize the connection between Practifi and Egnyte. The OAuth token is stored securely in Salesforce and does not expose your Egnyte admin password. However, if an unauthorized user modifies the Egnyte Configuration record, the integration could be compromised. Restrict access to the Egnyte Configuration object to system administrators only.

Remote Site Settings Security

Remote Site Settings allow Salesforce to connect to external domains. The settings are configured to use HTTPS (encrypted connections) and do not contain sensitive credentials. However, ensure that the domain names in Remote Site Settings match your actual Egnyte domain and the Egnyte API endpoint. Periodically verify that no unauthorized Remote Site entries have been added.

Permission Set and User Access Control

The Egnyte User permission set controls who can access Egnyte integration features within Practifi. Assign this permission set only to users who need access to Egnyte (advisors, support staff, compliance personnel). Review permission set assignments regularly and remove users who no longer need access to Egnyte.

Per-Record Permissions (Package v2.6.1+)

If your package version supports per-record permissions, use the Viewer, Editor, and Owner permission levels to limit user access on a per-record basis. For example, you might assign a back-office staff member as a Viewer on a sensitive client record while granting the primary advisor Editor access. This prevents unauthorized modifications while allowing necessary access.

Data Synchronization

The Egnyte integration syncs data between Practifi and Egnyte. Ensure that your organization’s data governance policies are followed: do not store highly sensitive information (such as passwords or API keys) in file names or folder names, as these will be visible in both Practifi and Egnyte. Train your team on proper document naming and classification.

Audit and Compliance

File activities in Egnyte are subject to Egnyte’s audit logging and compliance features. For regulated industries, verify that Egnyte’s audit trail meets your compliance requirements (e.g., SOX, FINRA, HIPAA). Review Egnyte’s security documentation and compliance certifications before deploying the integration to production.

---

Known Limitations

• SSO and 2FA Limitations During Setup: If your Egnyte organization uses single sign-on (SSO) or two-factor authentication (2FA), you may need to use a separate service account for the initial OAuth authorization. Contact Egnyte Support for guidance if you encounter authentication issues.
• Folder Template Limitations: Folder templates create a static structure when the record is linked. If you modify a folder template after records have already been linked, existing records are not updated retroactively. New records will use the updated template.
• File Size and Quantity Limits: While Egnyte supports large files and folders, extremely large files or folders with thousands of items may load slowly in the Egnyte Canvas. Organize files into reasonably-sized subfolders to maintain performance.
• Sandbox-to-Production Considerations: If you test the integration in a sandbox and later deploy to production, the Egnyte Configuration records, folder structures, and folder templates will not automatically transfer. You will need to recreate the Egnyte Configuration record and re-authorize the domain in production.
• Org-Level Configuration: The integration supports only one active Egnyte domain connection per Salesforce org. If your organization uses multiple Egnyte instances or domains, contact Egnyte Support to discuss multi-instance configurations.
• Prospect Conversion File Migration: When a Prospect is converted to a Client, files automatically follow the record to the Client folder structure. However, if a Prospect record was never linked to Egnyte (no folder was initialized), the conversion will not create a linked Egnyte folder for the new Client record. The advisor will need to manually initialize Egnyte on the Client record after conversion.
• Copy Link Button: This button is blocked by Salesforce in certain browsers. To work around this limitation, we suggest using keyboard shortcuts to copy links.
• Standard Users: The integration is not available for Standard Users except through Communities. 
• Egnyte Permission Sync: Revoking Salesforce access does not automatically revoke Egnyte permissions. These permissions must be revoked manually in addition to Salesforce access.
• Classic Mode Requirement: At this time, Engyte has established that domain configuration must be done in Salesforce Classic and requires users to switch between Classic and Lightning mode.

---

Frequently Asked Questions

Q: Can I use the integration if my Egnyte account uses single sign-on (SSO)?

A: Yes, but you may need a workaround for the initial OAuth authorization. If your admin account uses SSO, you may not be able to complete the “Authorize Egnyte” step directly. Contact Egnyte Support or your Egnyte account manager to request a service account with password authentication for the Practifi integration. Once authorized, all users can access Egnyte normally through the Egnyte Canvas.

Q: Can multiple users access the same Egnyte folder simultaneously?

A: Yes. If multiple advisors are assigned to the same Client record and all have Egnyte access, they will all see the same Egnyte folder when viewing that Client in Practifi. However, file-level permissions (if using package v2.6.1+) can be set on a per-user basis to control who can view, edit, or delete specific files.

Q: Is there a way to restrict which advisors can see which client files?

A: If your package version is 2.6.1 or later, you can set per-record permission levels (Viewer, Editor, Owner) to control access. For earlier versions, access control is based on the user’s Egnyte User permission set assignment. All users with the permission set can see all linked Egnyte folders. If you need fine-grained access control, contact Egnyte Support about upgrading your package version or implementing additional access control measures.

Q: Can I customize the folder structure or naming conventions?

A: The base folder hierarchy (Shared Directory → Salesforce.com → [Object Type] → [Record Name]) is fixed by the integration. However, you can create custom subfolders within each record’s folder, and you can use folder templates to standardize the subfolder structure when a record is linked. For more advanced customization, contact Egnyte Support to discuss options with the Egnyte engineering team.

Q: What happens if I change my Egnyte domain name?

A: If your organization changes its Egnyte domain, you will need to update the Egnyte Configuration record in Salesforce. Go to the Egnyte Configuration object, edit the domain field with your new domain, and re-authorize the connection by clicking the “Authorize Egnyte” button again. You will also need to update the Remote Site Settings to reflect the new domain name.

Q: Can I run the integration in a sandbox without affecting production?

A: Yes. You can independently install the managed package and configure the integration in a sandbox environment. The sandbox will have its own Egnyte Configuration record, remote site settings, and permission set assignments. A separate Egnyte domain or service account can be used for the sandbox, or you can use the same Egnyte domain with a separate authorization. Files created in the sandbox will appear in a separate folder structure within Egnyte. When you are ready to deploy to production, you will need to install the package and configure it in production separately.

Q: Does the integration support file versioning and version history?

A: File versioning is a feature of Egnyte itself, not the Practifi integration. Egnyte stores file versions and revision history. When you access files through the Egnyte Canvas in Practifi, you can see the current version. To access file history and previous versions, log in to Egnyte directly and use Egnyte’s version history feature.

Q: Is there a way to automate folder creation for bulk records?

A: The integration does not provide a built-in bulk initialization feature. Folders are initialized on a per-record basis when an advisor accesses the record and clicks the option to link it to Egnyte. If you need to initialize Egnyte for a large number of existing records, consider contacting Egnyte Support or a Practifi consultant to discuss bulk initialization options or custom automation.

Q: What Egnyte documentation should I reference for additional help?

A: Egnyte publishes comprehensive integration documentation on its support portal. For additional help with the Egnyte for Salesforce integration, visit Egnyte Support at support.egnyte.com or contact your Egnyte account manager. For Salesforce-specific questions, contact Practifi Support.