Expand my Community achievements bar.

Wondering how Workfront Proof works? Join our AMA on May 8th and ask our Community experts!

Locking Deliverables/Objects from Changes in Workfront

Avatar

Level 2

3/17/25

Summary Description of Your Idea

I propose a feature in Workfront that allows administrators to lock deliverables, objects, or specific project components from further edits after a defined cutoff time. This functionality would help teams, especially those managing time-sensitive deliverables, maintain consistency and prevent unauthorized or last-minute changes that could disrupt workflows. The goal is to ensure that once a project reaches a designated phase, certain users (e.g., Dentsu/PMs/Planner/CMs) can no longer make changes, while maintaining flexibility for those who still need access.

Why Is This Feature Important to You?

  • Prevents disruptions: Last-minute edits from external teams can disrupt Creative Services' workflow, leading to inconsistencies in project deliverables.
  • Ensures process integrity: Locking objects ensures that final versions remain untouched once a project moves to the next phase.
  • Reduces manual oversight: Currently, permissions must be updated manually, requiring extra effort to monitor and enforce deadlines.
  • Enhances collaboration: Allows teams to work freely within a defined timeframe but ensures stability after the cutoff date

How Would You Like the Feature to Work?

  1. Configurable Locking Mechanism:

    • Admins or project owners should have an option to set a lock date for specific deliverables, tasks, or documents.
    • Past this date, the defined objects become read-only for designated users or teams.
    • The ability to edit can still remain for admins or specific roles (e.g., Project Owners).
  2. User-Specific Access Controls:

    • Ability to lock objects for specific groups (e.g., Dentsu) while maintaining edit rights for internal teams.
    • A "Locked State" should be configurable within user access settings.
  3. Manual & Automated Locking:

    • Admins can manually apply a lock at any time.
    • Option to automate the lock based on project phases or due dates.
  4. Visual Indicator for Locked Items:

    • Clearly mark locked items with an icon or banner to indicate restricted access.
    • Provide an error message when restricted users attempt to edit locked objects.
  5. Audit Trail & Override Option:

    • Maintain a log of when an item was locked and by whom.
    • Allow authorized users (e.g., Creative Services leads) to override the lock in special cases.

Current Behavior

  • There is no direct way to lock deliverables, tasks, or objects from edits after a certain date. Teams must manually adjust permissions for users after deadlines, which is time-consuming and prone to human error.
  • Users with past access can continue making changes unless an admin removes their permissions.
  • There is no visual indication of an object being locked or restricted, leading to confusion.
  • While projects can be marked as Complete, this status change locks access for all users, rather than just a select group.
1 Comment

Avatar

Level 1

3/25/25

I second this update and think it will help with the tracking of issues and change logs. Meaning any changes requested need to sit as a request to the project and await approval or prioritization. Support previously suggested we use the field tracking feature, but there is a limitation to how many fields can be tracked.