## TL;DR
Grant the identity behind the API credentials access to the destination folder first. API calls run as a specific Looker user, and that user needs permission to create content in the target folder and to see the source dashboard and its model. Set the folder content access and the user model access, then retry the same API call without changing the payload.

```text
Looker API dashboard duplication failed: folder permission error how to fix
```

## Use this when
- An API script that duplicates dashboards fails with a folder permission error while reading dashboards works.
- The target folder is new, restricted, or was recently reorganised.
- The same duplication works in the interface under an admin account.

## Not for this skill when
- The API call fails authentication before reaching any folder check. Fix the API credentials first.
- The source dashboard itself cannot be read by the API user. Grant source access as well as folder access.

## Steps
1. Read the API error response and note the folder identifier and the user the call runs as. Verify: the error names the destination folder and the call identity is known
2. Open the folder access settings in the admin area and check which groups can manage content in that folder. Verify: the API user groups are absent or set to view only
3. Add the API user group with manage access for the target folder, or choose a target folder the automation already owns. Verify: the folder access list shows the group with the higher access level
4. Confirm the API user model access set includes the model the dashboard uses, since tile creation checks model access too. Verify: the user can run an explore on that model through the API
5. Retry the original duplication call with the unchanged payload. Verify: the call returns a new dashboard identifier in the target folder
6. Open the duplicated dashboard in the interface and confirm its tiles render for a normal viewer. Verify: the copy loads with data and sits in the intended folder

## Why it happens
Permission errors in automation are usually identity drift, the script runs as a user whose access was never designed, only accumulated. Giving the automation identity an explicit group, with folder and model access granted to that group on purpose, makes the next folder reorganisation a reviewable change instead of a midnight failure. The interface working under an admin account proves nothing about the API identity.

Looker folder permissions and model access sets decide what an API user can do, separately from what an interactive admin can do. Automation often runs under a service style user created for the task, and that user is easy to forget when folders are reorganised or a new target folder is created with restricted access groups. The API error names the folder because creation is the step that fails, even when reading the source dashboard worked.

Field notes for Looker specifically. The Admin area holds the diagnostic pages that matter here, System Activity for query history and runtimes, the PDT activity page for derived table builds, and the Content Validator under the content management tools. Keep the browser on the same Looker version as the instance when testing, because explore behaviour and error wording shift slightly between monthly releases. Screenshots from viewers are worth collecting with the exact load time, since Looker support and your own history search both work far better from a timestamp than from a description of slowness.

A practical habit for Looker teams is to keep one test user per permission tier and to test every model change as the most restricted tier, not as an admin. Admins bypass access filters, see every field, and hit warm caches, so admin testing systematically hides the failures viewers get. Pair that with a standing explore that lists the twenty slowest tiles across the instance each week, and most dashboard incidents become follow ups on a report the team already reads, instead of surprises reported by executives in a meeting.
## Variants and edge cases
### Looker API copy dashboard folder permission denied fix
The direct phrasing from the API error response.
### Looker duplicate dashboard API user cannot create in folder
The identity variant naming the API user as the missing piece.
### Looker automation folder access group manage content
The group design variant for durable automation access.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_K3mC5ikfAY3M6J12rBGI4A