Comment 3 for bug 1470373

Hi, Renat,

Actually, I am thinking of making it more flexible, more controllable to end users.

* When user A creates workflow/workbook/action via API, he can specify a param (e.g. 'scope=public' ) , then all the mistral users can see and use that resource user A created.
* User A created a 'private' resource as before, he makes a POST request to mistral, e.g. http://localhost:8989/workflows/123/members, with body content {"member": "user B"}, then user B accepts the sharing through some ways, then both user A and user B can see and use that resource.
* User A created a resource and share it with user B, but user B doesn't want to accept it, and user B could reject and can't see and user that resource.
* ...

thoughts?