Can I restrict edit permissions to a specific version?
Here is the use case. I have 2 versions of a document set--5.1 and 5.2. I am nearly finished with 5.1 and do not want certain authors to be able to edit 5.1. However, work has begun on 5.2 and I do want them to edit. Is there a way to do this?
-
Hi Robert,
it is possible to archive specific versions. Archived versions are not displayed in the working version drop-down. Please have a look at the following page in our documentation for further information: http://www.k15t.com/display/VSN/Archiving+Version
Does this help?
Cheers,
Nils -
Hi Nils,
we would like to restrict edit permissions to a specific version too. In our case we have an editorial deadline. After this deadline some checks are done, PDF files are created, and software and documentation are merged. Last checks of the result are done and then the release is officially released. At this time the Scroll publish process will be done too. Between deadline and release / publishing elapse altogether some days till a week.
In this time editing on the version to be published should be limited to very few technical authors. Nevertheless all colleagues should be able to read / check the documentation and to report possible faults to the technical authors. Therefore archiving the version is no solution for us.
Cheers,
Matthias -
Hi Matthias,
thanks for the information. We've already tracked this improvement in our JIRA system: https://k15t.jira.com/browse/VSN-17.
Please sign up at https://k15t.jira.com/secure/Signup!default.jspa to watch, to comment or to vote for this issue. The more votes an issue has, the more likely it is that it will implemented in one of the next releases.I hope that helps.
Cheers,
Nils -
Hi,
I have no permission to view this page https://k15t.jira.com/secure/Signup!default.jspa
Could you help to share the latest information of this topic?
Could we use REST API to restrict one version?
Could we restrict the page when publish it?
Thanks a lot.
-
Hi Helen,
Were you referring to this Jira issue - https://k15t.jira.com/browse/VSN-17 - Nils sent previously in the thread? If so, can you please confirm if you can access the link I inserted above?
This issue has now been resolved, and it is possible to restrict the editing of a space version directly through the UI. More specifically via the Manage restrictions option in Scroll Versions. You can restrict editing permissions to specific groups or specific users. If you add a group or user to a specific version, only this group or user is allowed to edit pages in this specific version. You can read more about it in this article: https://help.k15t.com/scroll-versions/latest/manage-versions-153651332.html
It is also possible to restricts space version using REST. Here is an example rest request that you can call:[POST] -H "Accept: application/json" -H "Content-Type: application/json" {baseUrl}/rest/scroll-versions/1.0/versions/{spaceKey}/restrictions
{"space":{"key":"TES4","name":"test4"},"versions":
[{"versionId":"7F00000101764E11B06474870D0BCA4F","editRestrictionGroups":[],"editRestrictionUsers":
[{"name":"vipuser","key":"4028929e75d0235e0175d02a0de5000c","fullName":"VIP User"}]},
{"versionId":"7F00000101764E120342CAAC26E0D0ED","editRestrictionGroups":[],"editRestrictionUsers":[{"fullName":
"VIP User","key":"4028929e75d0235e0175d02a0de5000c","name":"vipuser","isAvailable":true}]}]}You can change the payload data according to your space setup.Regarding application of restrictions during publishing. No this is, unfortunately, not possible. The restrictions would have to be applied directly within the space where the version is published.Let me know if this helps.
Cheers,
Johanna (K15t)
Please sign in to leave a comment.
Comments
5 comments