Sharing segment or workspace with users in other organization | Community
Skip to main content
Level 2
March 8, 2024
Solved

Sharing segment or workspace with users in other organization

  • March 8, 2024
  • 1 reply
  • 703 views

Hi people in AA comunity 😀

 

I'm finding a way to transfer segments & workspace to create the same workspace in another organization.

However, it seems that sharing any segments and workspace with the one in other organization is not possible at the moment.

Does anybody have found a way for it? It would be conducive if you share how you did that. 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by aa_from_savoy

Hi @nayoungki ,

you can share a project outside the organization by using the "Share" feature, that allow you to send a workspace in PDF or CSV format to anyone.

If you want to share an editable workspace outside the org, it's not possible. Same for the segments.

A possible solution is by using APIs:

  • download the segment definition via API from Org A
  • create a segment with the same payload in Org B

Same for the projects.

You need to carefully verify the ID references in the payload (especially for the projects) because they change from Org A to Org B.

Example: a workspace is using a custom daterange that have the ID XXX in Org A. In the payload, this must be replaced with YYY that is the id of that daterange in Org B.

 

Hope this helps.

 

best.

1 reply

aa_from_savoyAdobe EmployeeAccepted solution
Adobe Employee
March 8, 2024

Hi @nayoungki ,

you can share a project outside the organization by using the "Share" feature, that allow you to send a workspace in PDF or CSV format to anyone.

If you want to share an editable workspace outside the org, it's not possible. Same for the segments.

A possible solution is by using APIs:

  • download the segment definition via API from Org A
  • create a segment with the same payload in Org B

Same for the projects.

You need to carefully verify the ID references in the payload (especially for the projects) because they change from Org A to Org B.

Example: a workspace is using a custom daterange that have the ID XXX in Org A. In the payload, this must be replaced with YYY that is the id of that daterange in Org B.

 

Hope this helps.

 

best.