Update Teams for Book versions
Update the relationship between books and teams since we have new book versions.
@pokhi @John.kopanas @DioneMentis As confirmed in #1268 (closed) and as on the permissions sheet:
-
When the user clicks 'New version' and fills out the new version fields in the modal and saves, a new version is created. The user who created that new version has edit access to the new version (same as when a user creates a new book). -
As usual, as is the case for all books at present, the Org admin and Sys admins also have access to all versions of the book. -
PDF2XML vendors must have access to all PDF versions. -
Team members are not automatically copied across from book version x to book version y (We start with a new team in the new version). -
Once the new version is created, more people (e.g. editors) could be added to the new version team at that stage, in the usual way as we do for wholebooks. -
Given that each version will have a new team, team members of version x do not have access to version y. In the dropdown which shows all the versions of the book, alternate versions can be clicked, but if I'm not on the team of that version, I get a permissions message that I don't have access. -
Teams for older book versions should still be editable once a new version is created.