Issue Summary

The hook settings rest endpoint documentation states that REPO_READ is required to access the endpoint, but actually REPO_ADMIN is required.

Steps to Reproduce

1. Make a call to the rest endpoint as a REPO_READ user

Expected Results

The call succeeds

Actual Results

There is an authorisation exception

Workaround

Use a REPO_ADMIN user to access the REST endpoint.

The fix for this bug is for the documentation to be updated to reflect the actual behaviour