From c93d281aa67287229d8b78b1406cec5087b3200e Mon Sep 17 00:00:00 2001 From: Samantha Crespo <100810716+samkcrespo@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:17:39 -0800 Subject: [PATCH 1/2] Update roles.md - updated Engage destination role reqs --- src/segment-app/iam/roles.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/src/segment-app/iam/roles.md b/src/segment-app/iam/roles.md index 99ff337c53..2b872663f2 100644 --- a/src/segment-app/iam/roles.md +++ b/src/segment-app/iam/roles.md @@ -88,9 +88,12 @@ Only users with the Workspace Owner role can access the Privacy Portal. ## Roles for managing Engage destinations -Engage destinations aren't included in the Engage roles by default. Users with Engage roles (including the Engage Admin) need additional permissions for each Engage space they work with to manage that Engage space's destinations. - -Grant these users `Unify and Engage Admin` on the selected Engage space and `Source Admin` on the source named `Engage (space name)` to grant them access to the Engage destinations for that Engage space. +When managing destination connections within an Engage spaces, specific permissions are necessary for various actions. +- **Connecting or Disconnecting Destinations to Engage Spaces:** +- To allow a user to connect or disconnect destination instances to your Engage space, grant these users `Unify and Engage Admin` access for the specific Engage space, and `Source Admin` access for the source(s) linked to that Engage space, named `Engage (space name)`. +- **Managing Connections to Engage features (Computed Traits/Audiences/Journeys)**: +- To allow a user to attach or detach a destination that is already connected to your Engage space to specific Engage features like Audiences or Journeys, grant these users `Unify and Engage Admin` access on the selected Engage space. The `Source Admin` role is not necessary for this action. + ## Roles for connecting resources From ec0be9914598081da37e58324303cf32907d08e9 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 13 Nov 2024 14:04:28 -0500 Subject: [PATCH 2/2] Apply suggestions from code review --- src/segment-app/iam/roles.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/src/segment-app/iam/roles.md b/src/segment-app/iam/roles.md index 2b872663f2..cabff9486b 100644 --- a/src/segment-app/iam/roles.md +++ b/src/segment-app/iam/roles.md @@ -88,11 +88,9 @@ Only users with the Workspace Owner role can access the Privacy Portal. ## Roles for managing Engage destinations -When managing destination connections within an Engage spaces, specific permissions are necessary for various actions. -- **Connecting or Disconnecting Destinations to Engage Spaces:** -- To allow a user to connect or disconnect destination instances to your Engage space, grant these users `Unify and Engage Admin` access for the specific Engage space, and `Source Admin` access for the source(s) linked to that Engage space, named `Engage (space name)`. -- **Managing Connections to Engage features (Computed Traits/Audiences/Journeys)**: -- To allow a user to attach or detach a destination that is already connected to your Engage space to specific Engage features like Audiences or Journeys, grant these users `Unify and Engage Admin` access on the selected Engage space. The `Source Admin` role is not necessary for this action. +When managing destination connections in an Engage space, you may require additional permissions. +- **Connecting or disconnecting destinations to Engage spaces:** To allow a user to connect or disconnect destination instances to your Engage space, grant `Unify and Engage Admin` access for the specific Engage space, and `Source Admin` access for the source(s) linked to that Engage space, named `Engage (space name)`. +- **Managing connections to Engage features (Computed Traits/Audiences/Journeys)**: To allow a user to attach or detach a destination in your Engage space to specific Engage features like Audiences or Journeys, grant these users `Unify and Engage Admin` access on the selected Engage space. The `Source Admin` role is not necessary for this action. ## Roles for connecting resources