-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While creating a new annotation permissions are not set correctly #9
Comments
The The allowed values for the To make an annotation accessible to everyone, whether they are a member of the group or not, the permissions for the whole group need to be set. The group in question (https://hypothes.is/groups/q5X6RWJ6/elife) is world-readable, so everyone can read annotations that are shared with the group. Please let me know if this helps resolve your issue. |
@robertknight Thank you ! But instead of |
Ah, indeed! - Thanks for the correction and confirmation. I'm going to close this issue as resolved, but we need to do a better job of documenting the allowed permissions, or simply exposing the supported values in a more natural way (eg. an |
Using endpoint https://h.readthedocs.io/en/latest/api-reference/v1/#tag/annotations I want to create a new annotation.

I'm using API key as Bearer Token.
Request body looks like this:
Response data of registered annotation looks like this:

Permissions from response looks like this:

I want that annotation should be available for anyone, but instead it's private. Setting permissions explicitly in request body does not work.
The text was updated successfully, but these errors were encountered: