As part of the Roads Management Insights onboarding process, a representative from
Google works with you to obtain additional details about your project. This page
outlines the categories of information you are required to share during
onboarding.

## Provide jurisdiction details

Share information about your managed regions. See [Define
jurisdictions](https://developers.google.com/maps/documentation/roads-management-insights/jurisdiction)
for more details.

## Choose a cloud region

Choose a Google Cloud region from the list of BigQuery supported regions that is
geographically closest to where you'll access route data.

Since BigQuery does not support inter-regional data access, make sure your route
data resides within the same region from which it is accessed. This is also
where your historical data is stored. Ensure data storage in this region
complies with data-sovereignty rules.

If you already are a BigQuery user, consider your current region of choice to
make it easier to combine data to derive enhanced insights.

If your contract includes a Real-Time Operations package, you must also choose
Google Cloud region or regions for Pub/Sub. The list the Google Cloud regions
for Pub/Sub message storage is limited to certain regions. See [Configure
message storage
policies](https://cloud.google.com/pubsub/docs/resource-location-restriction)
for more details.

## Provide project number

Share your Google Cloud Project with your Google representative. The Google
Cloud Project number is used by Roads Management Insights for several purposes,
including:

1. Enabling project access to the Roads Selection API, facilitating the creation and management of designated routes. Keep in mind this project can be separate from the project number used to enable Google Cloud services.
2. Creating a private data exchange in Analytics Hub to host the historical table listing, following the naming convention: Roads Management - <var translate="no">PROJECT_NUMBER</var>.
3. Creating a BigQuery dataset of historical designated routes for the project. See [Accumulated road
   data](https://developers.google.com/maps/documentation/roads-management-insights/accumulated-data) for more information.
4. Creating a Pub/Sub topic for you to receive real-time data. See [Real-time
   road data](https://developers.google.com/maps/documentation/roads-management-insights/real-time-data) for more information.

## Provide Google Cloud Account emails

Provide the Google Cloud account email(s) of everyone that needs to access
Analytics Hub and BigQuery for road data analysis. Google representatives will
grant Analytics Hub's Subscriber role to the accounts you provide.

- **Google Account email address(es) for BigQuery access:** Provide the Google Accounts (can be Gmail or Google Workspace) that will be granted access to the data through BigQuery Sharing, also known as Analytics Hub. You can list multiple email addresses, separated by comma
- **Google Account email address(es) for Pub/Sub Subscriber role**: Provide the Google Accounts that will have Pub/Sub subscriber permission assigned.

The provided accounts must also have [required IAM
roles](https://cloud.google.com/bigquery/docs/analytics-hub-view-subscribe-listings#required_roles)
in your project to be able to access the data.