> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blockworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting Access

> Request the Blockworks Snowflake Datashare and mount it in your Snowflake account.

Access to the Blockworks Snowflake Datashare is arranged with our team. Once the share is granted,
mounting it in your account takes a few minutes and two SQL statements.

## 1. Request access

<Card title="Contact Blockworks" icon="mail" href="https://blockworks.com/contact">
  Get in touch at [blockworks.com/contact](https://blockworks.com/contact) to discuss datashare
  access.
</Card>

To speed things along, have the following ready:

| Detail                                | Why it is needed                                                                                       |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| Your Snowflake **account identifier** | In the form `<organization_name>.<account_name>`. The share is granted to this account specifically.   |
| Your **cloud provider and region**    | AWS, Azure, or GCP, and the region, for example `AWS us-east-1`. Determines how the share reaches you. |
| The **datasets** you need             | Access is scoped to the datasets covered by your agreement.                                            |

<Note>
  Find your account identifier by running `SELECT CURRENT_ORGANIZATION_NAME(), CURRENT_ACCOUNT_NAME();`
  in Snowflake, or by reading it from the account selector in Snowsight.
</Note>

<Warning>
  Snowflake Secure Data Sharing is direct only between accounts in the same cloud provider and
  region. If your account is in a different region, tell us up front. Cross-region delivery is
  arranged differently, and knowing early avoids a false start.
</Warning>

## 2. Find the share

Once we have granted the share to your account, it appears in your Snowflake account under
**Data Products**, then **Private Sharing**, in Snowsight, listed as a share awaiting setup.

To confirm it from SQL, use a role with the `ACCOUNTADMIN` role (or a role with the
`IMPORT SHARE` privilege):

```sql theme={null}
USE ROLE ACCOUNTADMIN;
SHOW SHARES;
```

The Blockworks share appears as an **inbound** share. Note its fully qualified name, the
`<provider_account>.<share_name>` value in the output. You will use it in the next step.

## 3. Create a database from the share

Mounting the share creates a read-only database in your account. Nothing is copied; the database is
a live view onto the shared data.

```sql theme={null}
USE ROLE ACCOUNTADMIN;

CREATE DATABASE BLOCKWORKS
  FROM SHARE <provider_account>.<share_name>;
```

<Note>
  `BLOCKWORKS` here is the local database name in **your** account, so pick whatever fits your
  naming conventions. `<provider_account>.<share_name>` is the value from `SHOW SHARES`.
</Note>

## 4. Grant access to your roles

A database created from a share is read-only, and its privileges are granted as a unit with
`IMPORTED PRIVILEGES`.

```sql theme={null}
GRANT IMPORTED PRIVILEGES ON DATABASE BLOCKWORKS TO ROLE ANALYST;
```

Repeat for each role that needs access. Grant to the narrowest set of roles that need the data.

## 5. Verify

```sql theme={null}
USE ROLE ANALYST;
SHOW SCHEMAS IN DATABASE BLOCKWORKS;
```

If you see the shared schemas, you are connected. Head to
[Querying in Snowflake](/datashare/snowflake/querying) to explore what is in them.

## Troubleshooting

<AccordionGroup>
  <Accordion title="The share does not appear in SHOW SHARES">
    Confirm you are running as `ACCOUNTADMIN`, and that the account identifier you gave us matches
    the account you are checking, since organizations often have several. If it still does not appear,
    come back to us with the exact identifier you ran `SHOW SHARES` in.
  </Accordion>

  <Accordion title="CREATE DATABASE FROM SHARE fails">
    This usually means the executing role lacks the `IMPORT SHARE` privilege, or the share name is
    not fully qualified. It must include the provider account prefix, exactly as `SHOW SHARES`
    reports it.
  </Accordion>

  <Accordion title="A user can see the database but not the data">
    Their role needs `IMPORTED PRIVILEGES` on the shared database. Ordinary object-level grants do
    not apply to shared databases.
  </Accordion>

  <Accordion title="Nothing works and the accounts are in different regions">
    Direct shares do not cross cloud regions. Contact us so we can arrange delivery for your region.
  </Accordion>
</AccordionGroup>

<Note>
  These are the standard Snowflake consumer steps for a direct share. If your organization has its
  own conventions for mounting shares (a dedicated provisioning role, a naming standard, an
  infrastructure-as-code workflow), follow those. The only Blockworks-specific inputs are the share
  name and the account identifier you give us.
</Note>