Product ideas | Community
Skip to main content

10000 Ideas

ChipAtDolGenNew Participant

Impersonate Users in AEPNew

DescriptionGiven the extensive/specific new facets of AEP and being able to have near limitless governance by Labels, its not sustainable to always give someone an access group or policy and assume that they won't accidentally see a field that they shouldn't have access to.  It would be great if we could "borrow" the same functionality that exists in AEM to log into AEP as a specific user to double check what they can see and do in AEP Why is this feature important to youThis would add a great measure of being able to audit users in an AEP tenant.  Our business uses Federated SSO and prohibits the granting of Personal Adobe IDs to Admin Console; this makes sure that only one person can only have one login.  This means in order to test is a policy is actually enforcing what it should, it requires 2 admins.  One to downgrade the other's access and another to do the actual test. How would you like the feature to workI personally would find it organic to go into AEP Permissions and select a user from that tool to impersonate and make sure that they can only see the right tools, fields and data sets.  But I can also see this being functional from Admin Console as well. Current BehaviourAs of today, we need to either ask the affected user/agency, that would personally benefit to having MORE access to our Platform data than LESS, to "confirm" that they only see what they need to see or would need 2 admins to spot check this by assigning the new policy to test in a controlled manner.

DavidGu11New Participant

Allow for a master control to block time entry on a specific project but allow for task creation & adjustmentsNew

Description -  We see a need for temporarily blocking time entry to a project but allowing the project owner to build and adjust the plan they're working on. Right now Dead and Complate statuses block time entry but also block most of the ability to manage and manipulate the project tasks.  It would be great to have some sort of master control that would allow blocking time entry across the project. We do want assignments to be in place to help us with resourcing and planning data but we do not want to accidentally have time put to the project before we're ready to fully activate it.  Once a user is assigned, they can generally find the project if they search and we regularly see people finding projects like this and logging time before the project has been activated. Why is this feature important to you - We regularly are trying to plan in advance of a project being activated. This requires building out a project plan and assigning resources and planned hours but we should not be recording time against the project yet. We currently have no way of blocking that time entry except by individually managing the permissions of the users being added to the project. But that creates a terribly burdensome amount of administrative work that you then have to manage later to add the ability to log time back to the users. It would be so much better if we had some other way to control whether the project accepted time entry and later flip the switch to activate it for time entry. How would you like the feature to work - Block time entry on the project from all users but all creation, editing and management of tasks and assignments. This could be done with a custom status where the status lets you prohibit time entry and moving to another status would activate the ability to do time entry. Or maybe just a master control in the project settings that allows/blocks time entry depending on whether you've toggled it. Current Behaviour - Any project that you can edit/add/manage the tasks on would also allow time entry from any resource assigned to a task and given the permission to log time.

Dominik_MarkoMiNew Participant

Revamp Company Folder Administration and BehaviourNew

Description & Current Behaviour - As stated in post https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-ideas/creating-shared-folders-in-adobe-analytics-outside-of-company/idc-p/724951 already the functionality of the Company Folder is very restrictive and doesn't make much sense:as stated in the existing thread, it should be able to give specific User rights (esp. editing rights) for various Subfolders (e.g., Marketing Team 1 has their own folder in the Company folder with their own reports which are then immediately shared with everybody in the Company because the reports are in the Company folder)Current state: such permissions are not available and only administrators are able to do anything with the Company folderWith this Status Quo comes the next problem that I've discovered: As an administrator I am able to see all Workspace projects of all users. I can also save over them and do anything I want with them. Except for on singular point: I am NOT able to move other users' projects into the company folder. The functionality is completely missing from the menu.I can only do it in the event that my administrator account gets "edit rights" for that specific projects (via the share menu). You know how I can get those rights? Exactly: as an administrator I am able to go into that project and give them to me myself. Only after doing that am I able to move the project into the company folder. Why is this feature important to you -The permission/right management of Adobe has never been a joy to work with. But getting this functionality and teasing things that absolutely make sense but hiding them behind so many walls and then making them unusable is frustrating. This makes the project management for the whole company simpler and more precise. How would you like the feature to work -Specific User rights/permissions can be given for specific subfolders. This way those members can add/remove projects from those subfolders and manage them themselves. This will also automatically share all the projects with the whole Company.Additionally to Users being able to do these things themselves, an Admin account should always by default be able to add/remove any project - be it shared or not with them - into the Company folder. 

Simon_U_LeNew Participant

Error Handling of Deactivated ResourcesNew

Description - There are actions that get blocked or error out when validating deactivated resources. The process should be smart enough to know if a resource is deactivated and remove that resource from the field rather than throwing an obscure error, ignoring the deactivated state, and creating a support issue. For example, when copying a project, and a resource manager on the project is deactivated, the copy fails at the end with an error saying the resource manager does not have a Plan account. This is meaningless and difficult to troubleshoot since the UI does not indicate that an assigned resource manager is deactivated. The copy process should realize this and simply remove the resource from the target or ignore the resource from validation since it was allowed on the source project anyway. Why is this feature important to you - The usability and error handling is not helpful and unnecessary stoppage of processes exist for situation that should be handled by code. How would you like the feature to work - If any resource during validation is a deactivated resource, it should either remove them from the process or ignore them from validation since nothing can be done with a deactivated resource. Current Behaviour - Tasks that validate resources stop an action due to a deactivated resource, but does not indicate that the resource is deactivated, creating a situation where it's unclear why the action failed.