Développer ma barre des réalisations de la Communauté.

Join our product experts for a live Ask Me Anything on November 12th at 8 AM PT about Experiences & Efficiency with AEP Agent Orchestrator & How Agentic AI is Fueling Smarter Testing and Growth!

Feature Enhancement: AJO- Folders with permission for organizing sandbox

Avatar

Level 1

Hello-


We have a client with multiple business units in one sandbox. As their data sits, it is not a good idea to separate into different sandboxes, so we hope to understand when foldering might be available in the user interface, especially for Journeys.

 

There are a lot of people working in the sandbox and they need to separate out their brands. Tagging only allows filtering, not foldering.  Allowing permissions for folder visibility is also necessary. 

 

Any input about how users have addressed this, and any roadmap info appreciated - we highly suggest this feature! 

Sujets

Les sujets facilitent la catégorisation du contenu de la Communauté et vous aident à retrouver le contenu le plus pertinent.

1 Reply

Avatar

Community Advisor

Hello @LeadousEx ,

Your scenario is very relevant for multi-brand or multi-business unit setups.

 

In AJO you do have role-based permissions , and you also have attribute-based access control.

However, even with these capabilities, you cannot define access at an individual journey level — for example, allowing one user to see only Journeys 1–5 and another to see Journeys 10–15. This type of object-level or journey-specific restriction is not currently supported in AJO.

 

Currently, there is no folder structure for journeys or the ability to restrict access by folder, brand, or business unit within the same sandbox. Tagging only allows filtering and does not provide access-level security.

 

The best available solution for you  is to create separate sandboxes for each brand or business unit. While this approach involves additional management effort, it remains the most effective way to ensure true separation and governance between teams.

Hope this helps clarify the current limitations and available options.

 

Best regards,
Parvesh

 

Parvesh Parmar – Adobe Community Advisor
https://www.linkedin.com/in/parvesh-parmar/