Skip to main content

Filter by idea status

10000+ Ideas

Ability to mail in a ProofNew

Description - We would like to be able to mail proofs into workfront, without having to log into the platform. Why is this feature important to you - We work with a lot of freelancers for artwork who are not users on Workfront. Pulling in their work into workfront involves a lot of time and effort that could be saved, instead of switching between apps, and checking in for updates, when all the other work is done in workfront. How would you like the feature to work - Something like ProofHQs now defunct functionality of being able to mail in proofs to a holding area or DropZone. Mailing to a specific person's DropZone url should provide the documents ready to be allocated to the right project in workfront. Each artwork manager can have their own separate DropZone, or even a central DropZone for the company with access restricted. The specific url for this landing page should be able to be emailed with the documents as an attachment in the email. The proof owner is the person who's DropZone is the target landing, and they can decide what to do with this proof within workfront. Current Behaviour - Once the job is completed, the process now involves these freelancers emailing the documents to the respective manager, who then uploads them into workfront. Which is very cumbersome. We are open to other alternatives, and haven't used the emailing feature in ProofHQ either, so any similar ideas that help bring in external work into workfront would be appreaciated.

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.

DavidGu11Level 2

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.