Skip to content
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

Be able to specify permissions on books / chapters / pages when using the API to import content #2702

Closed
Mynster9361 opened this issue Apr 21, 2021 · 2 comments

Comments

@Mynster9361
Copy link

API Endpoint or Feature

Be able to specify permissions on books / chapters / pages when using the API to import content

Use-Case

When you are creating or importing content and already know which group should have access to that specific group it would be nice to set it already in the import faze instead of having to do it manually after content has been imported.

Example.
You have a book with custom permissions on.
Within that book you have pages and chapters also with custom permissions.
So lets say you would like to add a chapter into a book but the content within the chapter needs to be reviewed before it gets released to everyone

Additional Context

I do not believe i have any further context to this

@abouchereau2
Copy link

Hi!
That would be awesome, I'm really looking for this feature.
Today, I don't know how to assign default permissions (to a known group) when creating a shelf or a book using the API.

@ssddanbrown
Copy link
Member

This has now been added within the work of #4099, and will be part of the next feature release so I'll therefore close this off.

This is done over a couple of new endpoints, including a PUT endpoint to set role-override permissions, fall-back permissions (Inheritance control) and owner user. You'd now be able to follow up your book/chapter/page create request with a PUT to the new endpoint to set permissions for that item as desired.

Additionally, Role API endpoints were added to the last release which may help here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants