I have one document library. Once item /document is created / uploaded, one task will be assigned to a Reviewer Group, at that time need to change the permission of an item for the user who has created item, to View only and for the Reviewer Group to Edit that item. If Reviewer has approved this task then again the permission of reviewer group will be view only and the Approver groups permission will be Edit. So I have to do this with designer 2013 workflow and without Rest API.
-
looks like repeating questions sharepoint.stackexchange.com/questions/154232/…– Akshay Dattatray NangareAug 18, 2016 at 6:49
-
I think that you have not read this question carefully. Read it once!!– RamAug 18, 2016 at 6:51
-
Now I have read the text "without Rest API". But Ram you have not read your previous questions properly. The first link you have mention in your previous question spsite.pro/Blog/Post/3/… in that article you can find line "There are no activities to break inheritance/assign permissions in SP2013 Workflows"– Akshay Dattatray NangareAug 18, 2016 at 7:01
-
"There are no activities to break inheritance/assign permissions in SP2013 Workflows. It’s possible to invoke 2010 Workflow with this activities but it’s complicated and not possible in Apps. Thus the only way is REST API." That means have one option of Rest!!– RamAug 18, 2016 at 7:04
-
You can create Custom action.– Akshay Dattatray NangareAug 18, 2016 at 7:20
2 Answers
Would Impersonation Step help?
The impersonation step runs as the last person who published the workflow and has the capability of removing permissions for an item/document:
Screenshot source: http://www.nothingbutsharepoint.com/2011/04/15/impersonation-in-sharepoint-workflows-an-interesting-pitfall-aspx/
Go to Site Settings>Site features> Enable 'Workflows can use app permissions' https://msdn.microsoft.com/en-us/library/jj822159.aspx
Add the impersonation step.
In the impersonation step, choose appropriate activity to remove/add permissions.
Here you have a sample user story: http://www.qdoscc.com/blog/sharepoint-tips-app-step-or-impersonation-step-sharepoint-designer-2013
-
-
There should be: Applies to Microsoft SharePoint Online, Microsoft SharePoint Server 2013, Microsoft SharePoint Designer 2013, Microsoft SharePoint Server 2010 support.microsoft.com/en-us/kb/2990213– grishaAug 19, 2016 at 10:01
-
If you are using 2013 workflow, the function has changed to "App Step", although Designer 2013 can still create 2010 workflow. App Step require to use whole bunch of REST API calls by HTTP actions.. Merit of using 2013 workflow over 2010 workflow? Future compatibility. I have no data whether 2013 style is better in performance.– satocAug 16, 2017 at 6:40
SharePoint Designer doesn't have an ability to manage permissions. To implement such user case I would offer you to use 3rd party tools.
Personally, I would recommend try Plumsail Workflow Actions Pack. It has permission management workflow actions.
I'm one of the members of the dev team product and I'm proud of it.
-
Do you offer it free of cost? I don't think that to purchase any third party tool!!– RamAug 19, 2016 at 13:02
-
-
Ram the option suggested by Roman may be good. you can use trial. Aug 19, 2016 at 13:13
-
-