From b177cabb67ca57b38a2aa310c95355b42c11eb96 Mon Sep 17 00:00:00 2001 From: rchinn-segment Date: Mon, 9 Oct 2023 13:23:58 -0700 Subject: [PATCH 1/4] update Snowflake setup doc --- src/unify/linked-profiles/setup-guides/snowflake-setup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/unify/linked-profiles/setup-guides/snowflake-setup.md b/src/unify/linked-profiles/setup-guides/snowflake-setup.md index 082435d2ca..baa6120ef0 100644 --- a/src/unify/linked-profiles/setup-guides/snowflake-setup.md +++ b/src/unify/linked-profiles/setup-guides/snowflake-setup.md @@ -38,11 +38,11 @@ Enter and run the code below to create a virtual warehouse. Linked Events needs ## Create a new role -Enter and run the code below to create specific roles for Linked Events. All Snowflake access is specified through roles, which are then assigned to the user you’ll create later. +Enter and run the code below to create specific roles for Linked Profiles. All Snowflake access is specified through roles, which are then assigned to the user you’ll create later. ```ts -- create role - GRANT ROLE segment_entities; + CREATE ROLE segment_entities; -- warehouse access GRANT USAGE ON WAREHOUSE segment_entities TO ROLE segment_entities; From 02ffe9457dde6ea936ce03b69034148600139f9f Mon Sep 17 00:00:00 2001 From: rchinn-segment Date: Mon, 9 Oct 2023 15:26:13 -0700 Subject: [PATCH 2/4] database access edits --- src/unify/linked-profiles/setup-guides/snowflake-setup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/unify/linked-profiles/setup-guides/snowflake-setup.md b/src/unify/linked-profiles/setup-guides/snowflake-setup.md index baa6120ef0..fe96de6361 100644 --- a/src/unify/linked-profiles/setup-guides/snowflake-setup.md +++ b/src/unify/linked-profiles/setup-guides/snowflake-setup.md @@ -48,8 +48,8 @@ Enter and run the code below to create specific roles for Linked Profiles. All S GRANT USAGE ON WAREHOUSE segment_entities TO ROLE segment_entities; -- database access - GRANT USAGE ON DATABASE segment_entities TO ROLE segment_entities; - GRANT CREATE SCHEMA ON DATABASE segment_entities TO ROLE segment_entities; + GRANT USAGE ON DATABASE TO ROLE segment_entities; + GRANT CREATE SCHEMA ON DATABASE TO ROLE segment_entities; ``` ## Create a new user From 9e9d7aae930ba8f146f6e9df6a8d1f19d0ec1cea Mon Sep 17 00:00:00 2001 From: rchinn-segment Date: Mon, 9 Oct 2023 16:52:02 -0700 Subject: [PATCH 3/4] Update Linked Events doc (PM feedback) --- src/unify/linked-profiles/linked-events.md | 23 +++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/src/unify/linked-profiles/linked-events.md b/src/unify/linked-profiles/linked-events.md index e35b1a247a..9560047ff8 100644 --- a/src/unify/linked-profiles/linked-events.md +++ b/src/unify/linked-profiles/linked-events.md @@ -35,18 +35,15 @@ Before getting started with Linked Events, you'll need: The following Segment access [roles](/docs/segment-app/iam/roles/) apply to Linked Events: -**Entities Admin Access**: Full CRUD (create, read, access, and delete) access to all Entities within a workspace. You can also grant or revoke user permissions. +**Entities Admin Access**: Entities Admins have the ability to view and edit entity models and connection details. -**Entities Read-only Access**: Read-only access to all Entities models and destinations in a workspace. +**Entities Read-only Access**: Entities Read-only users have the ability to view entity models. -For Linked Events, you need the following roles: -- `Workspace Owner` -- `Entities Admin` -- `Source Admin` +To create models and enrich events in destinations, you need the following roles: +- `Workspace Owner` and `Entities Admin` -To use Connections with Linked Events: -- `Workspace Owner` -- `Unify Read-only or Admin` +OR: +- `Unify and Engage Admin` - `Entities Admin` - `Source Admin` @@ -69,9 +66,17 @@ For Linked Events, the sync destination is an internal Segment data store. To tr You can choose which database within your warehouse this data lives in. +Linked Events uses Reverse ETL to compute the incremental changes to your data directly within your data warehouse. The Unique Identifier column detects data changes, such as new, updated, and deleted records. + +For Segment to compute data changes in your warehouse, Segment requires both read and write permissions to the warehouse schema table. At a high level, the extract process requires read permissions for the query being executed. Segment tracks changes to the query results through tables that Segment manages in a dedicated schema (for example, `_segment_reverse_etl`), which requires some write permissions. + +> warning "" +> Only sync what you need for enrichment. There may be cost implications to having Segment query your warehouse tables. + > info "" > Linked Events syncs data from your warehouse approximately once every hour. + ### Supported data warehouses The table below shows the data warehouses Linked Events supports. View the Segment docs for your warehouse, then carry out the corresponding steps. From 2a533ef3a597f4a9688dd295f984494b58be9fb2 Mon Sep 17 00:00:00 2001 From: rchinn-segment Date: Tue, 10 Oct 2023 09:06:15 -0700 Subject: [PATCH 4/4] Remove redundant section --- src/unify/linked-profiles/linked-events.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/unify/linked-profiles/linked-events.md b/src/unify/linked-profiles/linked-events.md index 9560047ff8..423f6a315e 100644 --- a/src/unify/linked-profiles/linked-events.md +++ b/src/unify/linked-profiles/linked-events.md @@ -62,10 +62,6 @@ To get started, you'll need to connect a data warehouse. Linked Events supports ### Schema -For Linked Events, the sync destination is an internal Segment data store. To track the data you send to Segment, you can view deltas/diffs in tables within a single schema Segment creates called `_segment_reverse_etl`. - -You can choose which database within your warehouse this data lives in. - Linked Events uses Reverse ETL to compute the incremental changes to your data directly within your data warehouse. The Unique Identifier column detects data changes, such as new, updated, and deleted records. For Segment to compute data changes in your warehouse, Segment requires both read and write permissions to the warehouse schema table. At a high level, the extract process requires read permissions for the query being executed. Segment tracks changes to the query results through tables that Segment manages in a dedicated schema (for example, `_segment_reverse_etl`), which requires some write permissions.