Set up the Integration User
Every storage provider other than Salesforce Files needs an Integration User before you connect it. Sliick Cloud Storage, Amazon S3, Azure Blob Storage, Google Cloud Storage and SharePoint all register your org with Sliick as part of setup, and that registration runs as this user. Set it up once. The Integration User field on the Storage Settings form then pre-fills on every later connect or reconnect, and you only enter it again to change it.
This is the step most often skipped. Without it, connecting fails with
Could not verify the provision challenge against the org., and on SharePoint the Create SharePoint Credentials button fails the same way.
What the user needs
Section titled “What the user needs”- A dedicated, active user. Not your own admin login, so the integration keeps working if an admin leaves. A user on the API Only Integration User profile is a good fit; the permission set below carries everything the integration needs.
- The Sliick Pipeline Integration permission set. Setup, then Permission Sets, then Sliick Pipeline Integration, then Manage Assignments, and add the user. This is the set setup requires. Sliick Files Setup and Sliick Files User do not cover it, and assigning one of those instead is the most common cause of the error above.
- Pre-authorised for the Sliick integration app. Setup, then External Client App Manager, then Sliick Pipeline Integration, and pre-authorise the user through its profile or a permission set.
- A licence seat, if your org assigns Sliick Files licences per user: Setup, then Installed Packages, then Sliick Files, then Manage Licenses. Without a seat, connecting fails the same way.
Where you enter it
Section titled “Where you enter it”On the Storage Settings tab in Sliick Settings, the connect form for every provider carries an Integration User field. Enter the user’s username there before you click Connect (or, on SharePoint, before Create SharePoint Credentials).
The two errors this step causes
Section titled “The two errors this step causes”| Message | What is wrong |
|---|---|
Set the Integration User before creating credentials | The Integration User field is blank |
Could not verify the provision challenge against the org. | The user is missing the Sliick Pipeline Integration permission set, a licence seat, or both |
Could not verify this org | The user is inactive, or is not pre-authorised on the Sliick integration app. Sliick signed in to your org successfully but could not confirm the registration |
Fix the cause and retry the same action. Registration is idempotent, so retrying is always safe.
What else the user does
Section titled “What else the user does”The same user is the one media processing acts as when it writes results back into your org, so nothing extra is needed for Media processing for images or for Sliick Photos.
Next: Choosing a storage provider.