Install S-Drive from the AppExchange

Login to Salesforce as Admin or as a special service user you’ve set up for S-Drive. If using a service user, it’s best to clone the System Admin profile and use it only for the service user.

Go to the AppExchange S-Drive listing and click “Get it Now.” Follow the prompts to install S-Drive in your sandbox or production org.

Activate S-Drive

After the installation is finished, go to S-Drive Configuration in your Salesforce instance:

The S-Drive Configuration tab will take you to a list of instructions as follows:

Step 1: Configure Remote Sites:


If Remote Site Settings are configured correctly, you'll see "Your remote site settings are configured correctly" message. If you see an error message in Step 1, resolve the issue by following the on-screen instructions.

Step 2: Configure Amazon S3 Credentials:

This step is required to connect your Amazon S3 account with S-Drive. You need to enter a valid "Amazon Access Key" and "Secret Key". After providing keys, if you see "Amazon S3 Credentials are configured correctly," continue with the next step.

 

Step 3: Configure Amazon S3 Bucket Name:

This is the bucket that will be used to store your files in your Amazon S3 account. You can configure more than one bucket. Bucket name must be unique and must comply with DNS naming conventions. Bucket names cannot have capital letters or underscores or contain dots (“.”)

You can select "Use existing bucket" or "Create a new bucket" option. We recommend creating your bucket here in the S-Drive Configuration, rather than directly in AWS or using a bucket previously created here.

If you configure more than one bucket, one must be chosen as the Default bucket. This will be used when no specific bucket is specified for upload.

Security: Your bucket access settings will be public by default when it is created. After it is created and you have finished the configuration process, there will be a button on the S-Drive configuration page under Authentication Settings called “Block Bucket Public Access” on the configuration page. Simply click the button to make your bucket private. This is recommended.

Step 4: S-Drive Connection: 

Click Connected Organizations link on the menu. Then under "Connect Salesforce.com Organizations", click either “Production Instance” or “Sandbox Instance” based on where you installed S-Drive. This redirects the salesforce.com login page.

NOTE: Portal Connection User Requirements

The user connecting S-Drive in the portal is typically an Admin User since the Admin installs S-Drive and then connects it in the portal as part of the installation.

However, the Portal Connection User need not have Modify All Data permission. Using a user that doesn’t have Modify All Data permissions increases security.

If you choose to connect in the portal with a non-Admin user, that user must still have

  • Customize Application permission

  • Send Outbound Messages permission

  • Access to S-Drive’s Apex classes (all start with “cg.” )

  • Access to S-Drive’s Custom Settings Definitions (all start with “SDRIVE.cg.”)

Back inside Salesforce, an Admin user will then need to go to S-Drive Configuration. They will be shown an Activation page with a button to click. Once the button is clicked, users will have access to S-Drive.

After entering login credentials, you’ll see your organization on the list of “Connected Salesforce.com Organizations.”


The user that connects the portal to your Salesforce org can not have the Session Security Level Required at Login (found in the profile under Session Settings) set to High Assurance. It should be set to None.

Step 5: Populate S-Drive Object List

S-Drive file objects must be added into a File Object List so S-Drive knows they exist.

Step 6: Add CSP Trusted Sites

Once these are set up, they take 10-15 minutes to take effect. During that time, if you upload a file to S-Drive, you will get an HTTP error.

A Note on Profile: Session Security Level Required at Login

Session Security Level Required at Login is a Session Setting in profiles that can be set to require 2 Factor Authentication. The profile of the user used to connect the portal must have this set to None (not High Assurance.)

Additionally, check Setup-->Outbound Messages. On each of S-Drive’s outbound messages, ensure the “user to send as” field is a user that does not have High Assurance. The outbound messages are:

  • AttachmentSync Callout

  • FileSizeRequest Callout

  • FileSync Callout

  • Preview Callout

Set up notifications to Admins when org is disconnected

If your org gets disconnected (for example, if there is a payment issue), S-Drive will no longer work until you reconnect. You can receive an email notification if this happens.

Congratulations! You are now ready to configure S-Drive to suit your needs.