Redshift Data Graph User Permission #7617
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
pwseg
requested changes
May 22, 2025
| ### Database | ||
| Create a separate databse for Segment usage (for example, `segment_workspace`). This will have the following schemas: | ||
| 1. Profiles Sync Schema (for example: `profiles_sync`) | ||
| * Segment will add [Profiles Sync tables](/docs/unify/profiles-sync/tables/) to this schema |
There was a problem hiding this comment.
Suggested change
| * Segment will add [Profiles Sync tables](/docs/unify/profiles-sync/tables/) to this schema | |
| * Segment adds [Profiles Sync tables](/docs/unify/profiles-sync/tables/) to this schema |
Or "Segment then adds..."
| 1. Profiles Sync Schema (for example: `profiles_sync`) | ||
| * Segment will add [Profiles Sync tables](/docs/unify/profiles-sync/tables/) to this schema | ||
| 2. `__segment_reverse_etl` schema | ||
| * Segment will create the [`__segment_reverse_etl` schema](/docs/connections/reverse-etl/system/#reverse-etl-schema) to add checksum tables for Linked/Data Graph |
There was a problem hiding this comment.
Suggested change
| * Segment will create the [`__segment_reverse_etl` schema](/docs/connections/reverse-etl/system/#reverse-etl-schema) to add checksum tables for Linked/Data Graph | |
| * Segment creates the [`__segment_reverse_etl` schema](/docs/connections/reverse-etl/system/#reverse-etl-schema) to add checksum tables for Linked/Data Graph |
| ### User | ||
| Have 2 roles assigned to the Segment user: | ||
| * Profiles Sync role (for example, `segment_profiles_sync_role`) | ||
| * Linked/Data Graph role (for example, `segment_linked_role`) |
There was a problem hiding this comment.
Suggested change
| * Linked/Data Graph role (for example, `segment_linked_role`) | |
| * Linked/Data Graph role (for example, `segment_linked_role`) |
Can we split this "Linked/Data Graph" out into "Linked Audiences and Data Graph" or something? I feel like the combo term "Linked/Data Graph" is very internal and wouldn't be clear to an external audience.
| The profiles sync role has the following permissions: | ||
| * Read and write access to the Profiles Sync schema (for example, `profiles_sync`) | ||
|
|
||
| #### Linked/Data Graph role (`segment_linked_role`) |
There was a problem hiding this comment.
Suggested change
| #### Linked/Data Graph role (`segment_linked_role`) | |
| #### Linked/Data Graph role (`segment_linked_role`) |
See above re: "Linked/Data Graph".
| * The second database has read access | ||
|
|
||
| ### Database | ||
| Create a separate databse for Segment usage (for example, `segment_workspace`). This will have the following schemas: |
There was a problem hiding this comment.
Suggested change
| Create a separate databse for Segment usage (for example, `segment_workspace`). This will have the following schemas: | |
| Create a separate database for Segment usage (for example, `segment_workspace`). This will have the following schemas: |
|
|
||
| Set up your Redshift Data Graph. You can choose from two different permissions options depending on your use case. | ||
|
|
||
| ## Permissions Option 1 |
There was a problem hiding this comment.
Suggested change
| ## Permissions Option 1 | |
| ## Permissions option 1 |
Should be sentence case
| * Read access to Profiles Sync schema (for example, `profiles_sync`) to read Segment Profile/Event tables that are created by Profiles Sync | ||
| * Read access to full user data schema (for example, devices schema) or read access to specific tables in the user data schema (for example, `user_devices` table or `device_locations` table) | ||
|
|
||
| ## Setup Guide |
There was a problem hiding this comment.
Suggested change
| ## Setup Guide | |
| ## Setup guide |
|
|
||
| 2. Select 1 of the options below: | ||
|
|
||
| a. (*Option 1*):: Assign the Linked/Data Graph role with read access to full user data schema |
There was a problem hiding this comment.
Suggested change
| a. (*Option 1*):: Assign the Linked/Data Graph role with read access to full user data schema | |
| a. (*Option 1*):: Assign the Linked/Data Graph role with read access to full user data schema |
Is "full user data schema" a term product is wanting us to use? I find this a bit confusing, maybe something like "access to all tables in the user data schema" would make more sense?
| Set up the Data Graph so that Segment has access to a single database. | ||
|
|
||
| ### Database | ||
| Create a single database for Profiles Sync & Linked usage (for example, `segment_workspace`). This has the following schemas: |
There was a problem hiding this comment.
Suggested change
| Create a single database for Profiles Sync & Linked usage (for example, `segment_workspace`). This has the following schemas: | |
| Create a single database for Profiles Sync and Linked Audience usage (for example, `segment_workspace`). This has the following schemas: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Merge timing
Related issues (optional)