Databricks screenshots

A data and AI platform for data engineering, analytics and machine learning at scale.

Databricks

Partner Connect provisions the warehouse side before you sign up

Databricks creates the user, token and privileges for dbt Cloud or Fivetran, passes them over, and the partner only asks for an account name and password.

B2BactivationonboardingMar 2025

01

Connect to partner: what will be created

Before anything happens, the side panel lists the user, privileges and token Databricks will create for dbt Cloud.

Databricks: Connect to partner: what will be created
  1. 1

    Consequence stated first (working)

    "By clicking Next, Databricks will create the following resources" says what Next does before you press it.

    Transparency

  2. 2

    Exact privileges as chips (working)

    USE CATALOG, CREATE SCHEMA, SELECT and CAN USE are scoped to named objects, so an admin can approve at a glance.

    Informed consent

  3. 3

    Token handled for you (working)

    "<Autogenerated and managed>" removes the step where most people get stuck: creating and pasting a token.

    Reduce friction

  4. 4

    Marketing blurb, twice (not working)

    The same dbt Cloud description repeats on the page behind; the space could explain what you get after connecting.

    Signal vs noise

02

Resources created, hand-off to dbt

Databricks reports the resources are ready and shows every connection detail it will pass to dbt Cloud.

Databricks: Resources created, hand-off to dbt
  1. 5

    Done before you ask (working)

    "Databricks has created resources" means the hard setup already happened on the warehouse side.

    Endowed progress effect

  2. 6

    Email prefilled (working)

    Your Databricks email carries over, so the partner account starts with known identity.

    Default effect

  3. 7

    Details with copy buttons (working)

    Hostname, port, HTTP path, cloud and region are visible and copyable for anyone who needs to set it up by hand later.

    Recognition over recall

  4. 8

    Six-line legal paragraph (not working)

    The data-sharing consent is a dense block right above the CTA, so most people will scroll past it.

    Cognitive load

  5. 9

    CTA names the destination (working)

    "Connect to dbt Cloud" says where you go next, not just "Next".

    Clear call to action

03

Taking you to dbt Cloud

A redirect interstitial shows the Databricks to dbt hand-off with both logos.

Databricks: Taking you to dbt Cloud
  1. 10

    Says what is happening (working)

    "Taking you to dbt Cloud's sign up page" explains the context switch so the new tab is not a surprise.

    Visibility of system status

  2. 11

    Logo-to-logo arrow (working)

    Databricks, arrow, dbt: the direction of the hand-off is readable without text.

    Mental models

  3. 12

    about:blank in the URL bar (not working)

    The page has no address while it loads, which looks odd on a flow that just shared credentials.

    Trust signals

04

dbt Cloud: complete registration

dbt Cloud only asks for an account name and a password; the email and Databricks link come in through the URL.

Databricks: dbt Cloud: complete registration
  1. 13

    Email locked in (working)

    The email is prefilled and greyed out, so one field is already done.

    Endowed progress effect

  2. 14

    Helper under the field (working)

    "This is usually your company name" answers the obvious question before it is asked.

    Contextual help

  3. 15

    Still a new password (not working)

    After a token-based hand-off you still create and confirm a password; SSO from the partner would skip this.

    Reduce friction

  4. 16

    Typo in the welcome (not working)

    "DatabricksPartner Connect" is missing a space on the first screen of the partner product.

    Aesthetic-usability effect

05

Connection succeeded, plus a survey

Back in Databricks, the success panel asks two questions about whether the hand-off worked.

Databricks: Connection succeeded, plus a survey
  1. 17

    Clear success state (working)

    "Connection succeeded" closes the loop in the tab you started from.

    Visibility of system status

  2. 18

    "You should have a new tab" (not working)

    Hedged copy admits the redirect may have failed; "here" is a weak fallback link.

    Clarity

  3. 19

    Asks if signup worked (working)

    Databricks measures the partner's funnel at the exact point it can break.

    Fake door test

  4. 20

    Asked too early (not working)

    "Were you able to complete your workflow" comes seconds after connecting, before any workflow could run.

    Contextual timing

  5. 21

    Specific failure reasons (working)

    "Missing privileges", "Couldn't sign into dbt Cloud" turn a vague no into a fixable bug report.

    Visibility of system status

  6. 22

    Opt out of the survey (working)

    "Don't show this next time" respects people who connect partners often.

    User control and freedom

06

Landing in a dbt Cloud trial

The new dbt Cloud account opens on a dashboard named after the Databricks trial, with a 14-day Team plan clock.

Databricks: Landing in a dbt Cloud trial
  1. 23

    Trial clock and pricing (working)

    "14 days left in your Team plan trial" with a Plans & Pricing link, without blocking anything.

    Transparency

  2. 24

    Context carried over (working)

    The project is called "Databricks Partner Connect Trial", so you know where it came from.

    Preserve context

  3. 25

    First nudge is the CLI (not working)

    The hero card pushes Cloud CLI setup with "Supercharge" copy instead of running a first model on the Databricks data you just connected.

    Time to value

  4. 26

    Empty chart, no next step (not working)

    "No data available" on an empty axis takes space without telling you how to fill it.

    Time to value

07

Integration page after connecting

The marketplace listing now shows the workspace is connected and offers a way back in.

Databricks: Integration page after connecting
  1. 27

    Connected badge (working)

    "This workspace is connected to the integration" confirms state on return visits.

    Visibility of system status

  2. 28

    Open integration (working)

    The primary button changes from connect to open, so the page becomes a launcher.

    Preserve context

  3. 29

    Nothing about your setup (not working)

    The main column repeats the blurb; it never shows which user, warehouse or token was created.

    Transparency

08

Add data hub

The Add data page groups native connectors, file uploads and Fivetran partner connectors on one screen.

Databricks: Add data hub
  1. 30

    Search first (working)

    "Search data sources" sits above the tiles for people who already know what they need.

    Discoverability

  2. 31

    One lonely native tile (not working)

    Databricks' own connector section has a single Salesforce tile marked Preview, which makes the native catalog look thin.

    Framing

  3. 32

    Files as the easy path (working)

    Upload and S3 tiles each have a one-line description of what they create.

    Flexibility and efficiency of use

  4. 33

    Partner connectors by logo (working)

    OneDrive, Google Drive, Jira, GitHub and Webhooks via Fivetran, with "See all" for the long tail.

    Recognition over recall

09

Connect data source via partner

Picking Google Drive opens the same partner panel, now showing the data path through Fivetran.

Databricks: Connect data source via partner
  1. 34

    Data path as a diagram (working)

    Google Drive, Fivetran, Databricks with arrows shows the middleman before you agree to it; the source label truncates to "Google ...".

    Mental models

  2. 35

    Token disclosure (working)

    "A personal access token is generated on your behalf and securely shared with Fivetran" says what will happen to your credentials.

    Transparency

  3. 36

    Generic Next (not working)

    "If you want to continue, click Next" restates the button instead of naming the action.

    Clear call to action

10

Hand-off to Fivetran

The confirmation step reuses the dbt template: email, connection details, legal text and a named CTA.

Databricks: Hand-off to Fivetran
  1. 37

    Email prefilled (working)

    Same as the dbt flow, the Fivetran account starts from your Databricks identity.

    Default effect

  2. 38

    One template for all partners (working)

    Token, hostname, port, HTTP path, cloud and region in the same layout as dbt, so the second connection feels familiar.

    Consistency and standards

  3. 39

    Legal wall again (not working)

    Six lines of liability text sit between the details and the button.

    Cognitive load

  4. 40

    "Connect to Fivetran" (working)

    The CTA names the partner you are about to leave for.

    Clear call to action

Takeaways from Databricks

  1. If you own one side of an integration, create the user, token and privileges yourself and pass them over, so the partner signup is two fields.
  2. List the exact permissions you will grant before the click, as scoped chips an admin can read in seconds.
  3. Ask whether the hand-off worked with specific failure reasons, but only ask about the workflow once the user has had time to run one.

Databricks

Demo center pages where the video is the page

Databricks' demo center opens each product demo as a full-width video, with the trial button kept in the nav.

B2BactivationNov 2024

01

AI-Powered Data Warehousing demo

The demo page is almost entirely a large embedded video.

Databricks: AI-Powered Data Warehousing demo
  1. 1

    Tagged demo traffic (working)

    "itm_data=demo_center" in the URL lets Databricks attribute sign-ups to the demo center.

    Human in the loop

  2. 2

    Trial button in the nav (working)

    "Try Databricks" stays in the header in brand red, so the next step is always there.

    Clear call to action

  3. 3

    Video fills the page (working)

    No hero copy or form in the way: the demo is the first and only thing you see.

    Visual hierarchy

  4. 4

    YouTube chrome (not working)

    "Watch on YouTube" and "Watch later" invite people to leave for YouTube.

    Signal vs noise

Takeaways from Databricks

  1. Make the demo the whole page and drop the gated form.
  2. Keep the trial CTA in the persistent nav so it's there when the video ends.
  3. Use a self-hosted or stripped-down player so the demo doesn't send traffic to YouTube.