Yes, workspaces or using properties helps in filtering activities for different users. Hopefully, this kind of implementation will be available for all features of Target to get the whole multi-tenancy experience. Thank you! 

Hello, It's more of the "SEE/ ACCESS" scenario. We would want to have multiple tenants/clients with using or maintaining only one Adobe Target account.That would mean:1. client1 users will only see client1 activities, offers, catalogue, etc.2. client2 users will only see client2 activities, offers, ...

Description - Currently, there are a handful of limitations when just using the properties and workspaces method to attain multi-tenancy in Adobe Target with one instance. Why is this feature important to you - We are trying to accommodate several tenants or clients with one instance of Adobe Target...

Hello @Cedric_Latimier_, This is for the metadata schema editor when creating fields and changing the rule settings for the fields. 

Request for Feature Enhancement (RFE) Summary:Ability to choose multiple options in defining rules with an "OR" logicUse-case:To be able to create "Requirement" and "Visibility" rules that would allow multiple options, with an OR logic so that we don't need to create the same field for the same rule...

Request for Feature Enhancement (RFE) Summary:Fix overlapping elements in metadata schema editorUse-case:To have a better user experience in using the metadata schema editorCurrent/Experienced Behavior:Currently, there are some overlapping elements in the metadata schema editor. Some of these exampl...

Request for Feature Enhancement (RFE) Summary:Better UI experience for Settings and Rules section in the metadata schemaUse-case:To be able to create metadata schemas easier and fasterCurrent/Experienced Behavior: 1. When scrolling to the bottom of the metadata schema form (especially when it has nu...

Request for Feature Enhancement (RFE) Summary:Ability to control "Requirement" and "Visibility" field settings for dropdowns linked to a JSONUse-case:To be able to reference a dropdown that uses a JSON for another field's "Requirement" and "Visibility" field settingsCurrent/Experienced Behavior:We c...

Request for Feature Enhancement (RFE) Summary:"Build Form" should "stick" on the metadata schema editor pageUse-case:To be able to create metadata schemas easierCurrent/Experienced Behavior:When we are creating metadata schemas that have a lot of fields, it is cumbersome to drag the field from the t...

Request for Feature Enhancement (RFE) Summary:Default option values when creating dropdown options in the metadata schema editorUse-case:To be able to create metadata schemas faster especially when creating dropdowns with a lot of optionsCurrent/Experienced Behavior:When creating dropdown options, w...