You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,34 +4,33 @@ redirect_from:
4
4
- '/reverse-etl/bigquery-setup/'
5
5
---
6
6
## Constructing your own role or policy
7
+
7
8
> warning ""
8
9
> You need to be an account admin to set up the Segment BigQuery connector as well as write permissions for the `__segment_reverse_etl` dataset.
9
10
10
-
When constructing a role and service-account we provide guidance for two approaches:
11
-
1. Grant full access - this approach gives Segment all the required permissions and is slightly faster as it also gives us to permission to automatically complete the setup for you.
12
-
2. Grant limited access - this approach is more secured, but because of the limited access we have, we require few additional one time setup steps from you.
13
-
14
-
You can choose whatever works best for you and skip the other step.
11
+
When creating a role and service-account, we offer two approaches:
12
+
1.**Grant Full Access**: This option provides Segment with all the necessary permissions and allows us to complete the setup for you automatically. It's the quicker option, requiring minimal effort on your part.
13
+
2.**Grant Limited Access**: This option is more secure, as it restricts permissions. However, due to the limited access, a few additional setup steps will need to be completed manually by you. These are one-time steps, and we will guide you through the process.
15
14
15
+
You are free to choose the approach that best suits your needs, and can skip the other.
16
16
17
-
### Grant full access
17
+
### Grant Full Access
18
18
With this approach we will use BigQuery predefined roles:
19
19
1. Navigate to **IAM & Admin > Service Accounts** in BigQuery.
20
20
2. Click **+ Create Service Account** to create a new service account.
21
-
3. Enter your **Service account name** and a description of what the account will do.
21
+
3. Enter your **Service account name** and a description of what the service-account will do.
22
22
4. Click **Create and Continue**.
23
23
5. Click **+ Add another role** and add the *BigQuery User* role.
24
24
6. Click **+ Add another role** and add the *BigQuery Data Editor* role.
25
25
7. Click **Continue**.
26
26
8. Click **Done**.
27
27
28
-
### Grant limited access
29
-
With this approach we will use costume role with the below permissions:
28
+
### Grant Limited Access
29
+
With this approach we will use custom role with the below permissions:
30
30
31
31
Permission | Details
32
32
---------- | --------
33
33
`bigquery.datasets.get` | This allows Segment to determine if the `__segment_reverse_etl` dataset exists.
34
-
`bigquery.tables.create` | This allows Segment to determine if the tables Segment uses to track state in the `__segment_reverse_etl` dataset exists.
35
34
`bigquery.jobs.create` | This allows Segment to execute queries on any datasets or tables your model query references, and also allows Segment to manage tables used for tracking.
0 commit comments