Revision access is based on record-level permissions instead of the global harvester curator permission.
If a curator has access to a record, they can view its revisions. If not, the API returns 403 (expected behavior).
The issue is that the Harvester Reports UI does not handle this 403 properly, so the error is unclear to the user.
Revision access is based on record-level permissions instead of the global harvester curator permission.
If a curator has access to a record, they can view its revisions. If not, the API returns 403 (expected behavior).
The issue is that the Harvester Reports UI does not handle this 403 properly, so the error is unclear to the user.