Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

Jennifer_Dungan
Jennifer_DunganNew Participant

Component Permission Improvements: Allow items to be attached to multiple suites, or allow virtual suites to inheritNew

Description - Permissions for segments / calculated metrics / etc are explicitly connected to the one suite under which it is created. On the surface, this makes sense... but many companies use Virtual Suites to control access to specific sites or regional variations within their global footprint... however, unless those users are granted access to the main global suite, they cannot use/access components (even when explicitly shared to those users).   Being able to explicitly choose multiple suites on a component (particularly something based on completely "global" dimensions or metrics - like a "Referrer: Google" segment, or a PVs/Visits metric that could apply to any tagging profile) should be accessible from multiple suites.    At the very least, there should be a way to all all virtual suites created from the main to have access, even if the main suite is not part of the user's permissions.   Creating multiple copies of a segment or metric to use on every suite or virtual suite is massive overhead - sure, the component can be copied and a new suite can replace the old; but when an update has to be made, someone has to go through every item to apply the changes (and ensure that those changes are made exactly the same and to all variants).   Segments, Calculated Metrics and other components need to be more flexible to allow us to maintain clean, optimized organization and sharing capabilities to ensure we don't have to repeat work and effort unnecessarily.    Why is this feature important to you - The Components have come a long way from how they used to be, but there is still room for improvement to allow proper cross suite usage and permissions.   Admins shouldn't have to choose between proper suite permission settings or having to duplicate efforts (and making maintenance so much harder) in order to ensure their users can access the segments or calculated metrics they need.   How would you like the feature to work - I would like there to be a multi-suite selection available on components... where an item uses something specific to one tagging profile, this would allow only one or 2 suites to be connected. But for truly shared contents, being able to select all matching suite profiles would be best. There could also be an option to "auto-select" all sub-virtual suites from a global suites as part of the permission levels.   Current Behaviour - Only one suite can be selected per component...  while the components can be used on any suite, they can only be used if the user has permissions to the main selected suite of the component....    The Select Tracking Suite should be a multi-selection list, not just a single selection.

Adilos-Cantuerk
Adilos-CantuerkNew Participant

Optimizing the Download optionsNew

Zusammenfassung der Funktionsverbesserungsanfrage (RFE): Currently the system only delivers ootb the option to download - Renditions (which include every rendition, even the unnecessary system renditions like for example the thumbnails) - Smart Crops (which include ALL the smartcrops)- Dynamics (were Presets can only get downloaded one at a time)  Anwendungsfall: A User wants to download 100 pictures, but only a specific rendition or smartcrop. Lets say the16:9 Smartcrop for all of them.  Aktuelles/erlebtes Verhalten: The Download option does not tell the user what this all contains.He will get every available rendtion (even those that are only useful for the system) and every smartcrop that is available for his selection. He does not see which options his download will contain. He can not opt out of the unnecessary options. Verbessertes/erwartetes Verhalten: The download dialoge needs to have sub-options that make it possible for the user to only download what he wants. It should be possible to limit the renditons in this sub-options dialoge, so the system renditions are not automaticly in the download. The Dynamic Presets should be also be available as checkboxes, so the user can download multiple presets at a time.Also, the image modifier pannel is not very user friendly. For example, the https://landing.adobe.com/en/na/dynamic-media/ctir-2755/dynamic-assets.html site displays how such a selector could look like. Choose your own Background, quality factor, format... It is hard to demand from every user to understand the image modifiers and them use them correctly Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): 2023.9.13665.20230927T063259Z Name des Kunden/der Organisation: medi GmbH & Co. KG Screenshot (sofern zutreffend):   Code-Paket (sofern zutreffend):  

Admin-console: Being able to assign permissions to groups for Administrator-Roles and "AdobeIO Developers" - and to enhance permission handing in AdobeIO-DeveloperConsoleInvestigating

Request for Feature Enhancement (RFE) Summary: 1) Being able to assign permissions to groups for Administrator-Roles and "AdobeIO Developers" 2) to enhance permission handing in AdobeIO-DeveloperConsole Use-case: Imagine: 20 program, 20 different partner-companies. Every partner has 10 developers and devops whom might need to raise tickets for their environment (1 out of 20). The role to be able to Create or See support tickets is "Support Administrator". Generally one would think to create 20 groups and add 10 people to each of these groups. These groups allow : AEM Administrator access (on DEVs and STAGE) Support Administrator permissions But this is NOT possible! You need to create these 20 groups and assign 10 people each.But then you have to add "Support Administrator" to 200 individuals separately.That makes NO SENSE!   In AIO-developer-console it is similar - as all these DEVS cannot be given "Full admin in the ORG".Now you need 3 devs for each project to be able to create and maintain AIO-projects.The assignment could again be done using groups (one would think) - but one needs to do that individually!And - once a project in dev-console is created by one dev (once he has the right permissions - and some APIs do not even provide profiles!) - only THIS developer and the FULL-ADMINS can edit/maintain this project.All other developers only have READ ONLY to the project - and would have to recreate it to make changes!   Current/Experienced Behavior: current understanding and behavior:"when you add an admin, you will select one account for the job, not a group. there's no other option in admin console for this" Improved/Expected Behavior: Being able to assign permissions to groups for Administrator-Roles and "AdobeIO Developers" Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Various  Screenshot (if applicable):   Code package (if applicable):