Adobe Experience Cloud
Workfront Coworker write access needs a live approval test
A Workfront MCP write toggle alone does not prove Coworker can update a real issue or parse IDs from a CSV.
November 17, 2026
A Workfront administrator enabled MCP write tools, supplied issue IDs, and still heard that Coworker lacked write access. The Experience League discussion ended with a useful distinction: a direct issue update prompted for approval and worked; the earlier input had been a CSV of IDs. This is an input-and-approval diagnosis, not evidence of a general outage.
Test one object before a batch
Choose one harmless custom field on a test issue. Give Coworker the issue ID in plain text, ask it to state the proposed value, and watch for the explicit write approval. Approve only that test action, then read the issue back in Workfront. If this works, the write path is available and the CSV parsing or batch instruction needs a separate test.
Separate tool exposure from object permissions
Adobe's MCP tool reference says write tools are disabled by default and toolset selection does not grant Workfront permissions. Check the system preference, the connected user's access level, the particular object's sharing, and whether the requested action appears in the exposed toolset. Capture the actual denial text rather than inferring the cause from the toggle alone.
Stage batch updates with a review ledger
For a CSV-driven update, first parse the file into a visible list of issue IDs and proposed field values. Reject missing, duplicate or cross-project IDs. Run a single-row approval test, then process a small batch with per-row readback and a failure list. A human should know exactly which objects will change before the assistant asks for approval.
Adovo’s view
An AI write permission is a gate, not a guarantee. A trustworthy agent makes the target, proposed change and approval visible before it touches operational data. When a single issue works and a CSV does not, debug the input boundary instead of widening access.
