Partner journey
What the Access SDK gives your users and how your product goes live, explained without code.
This page is for product, sales, and project leads. Developers start at Get started.
What your users get
Your users browse, search, and download files from their company's content systems without leaving your product: a DAM (digital asset management system), a MAM, cloud storage, or a CRM. CI HUB connects to more than 70 of them, including Adobe AEM, Bynder, and Sitecore, so your developers build one integration instead of one per system. In the steps below, "DAM" means any of these systems.
In your product, a user:
- Picks their DAM from a list.
- Logs in on the DAM's own login page, with the DAM account they already have.
- Browses folders, searches by keyword (or by a similar image, where the DAM supports it), and downloads what they need.
Users log in at the DAM themselves, so the DAM's own access rules apply. Files come straight from the source, so users always get the current, approved version. Next to each file your product can show a thumbnail, the metadata and keywords from the DAM, and the other versions the DAM offers, such as a smaller size or another file format.
The Access SDK is read-only today. Users find and download files. They can't upload or change them yet. New capabilities appear in the changelog as they ship.
What you need on your side
- Someone who agrees on the commercial terms with CI HUB.
- A developer who can work on your servers. The part that tells CI HUB who your users are runs there, not in the browser.
- A technical contact person for CI HUB.
The journey at a glance
Everything is built and checked on stage, CI HUB's test environment, before it moves to production, the live environment your customers use.
Step by step
Agree on commercial terms
- Who
- You and CI HUB
- Done when
- Your company has an active Access SDK subscription.
- Contact
- sales@ci-hub.com
CI HUB sales sends you a quote. Your developers can read all of this documentation before you sign.
Register your product
- Who
- You and CI HUB
- Done when
- CI HUB confirms your stage access.
- Contact
- Your CI HUB contact
Your developers send CI HUB a short list of technical details, listed on Partner registration, plus a technical contact person. You never send CI HUB passwords or secret keys.
CI HUB then registers your product, sets up your account, and tells you when stage is ready.
Build on stage
- Who
- You
- Done when
- On stage, a user of your product can connect a DAM and see its files.
- Contact
- Your CI HUB contact
Your developers build three parts:
- User handoff. Your servers tell CI HUB which of your users is making the request. Your users never see this part.
- DAM login. Your product opens the DAM's login page and remembers the connection.
- Content. Your users browse, search, and download inside your product.
TypeScript and JavaScript teams get a ready-made client library that handles most of this. Any other language uses the same API directly. If your developers work with an AI coding assistant, they can connect it to these docs.
Verify on stage
- Who
- You
- Done when
- The checks pass and you've told your CI HUB contact.
- Contact
- Your CI HUB contact
On stage, a test user of your product connects a DAM, logs in there, and then opens a folder, runs a search, or downloads a file.
You don't submit code to CI HUB. You host your product and release it on your own schedule.
Go live
- Who
- You and CI HUB
- Done when
- Your product works in production.
- Contact
- Your CI HUB contact
CI HUB copies your setup to production and agrees on a handoff date with you. On that date your developers switch your product from the stage address to the production address and run the same checks again.