*@ by Hexigo <https://mailapp.hexigo.com/#/register>*
On Mon, Oct 26, 2015 at 4:18 PM, Shiro Kulatilake <[email protected]> wrote: > Hi Mushtaq, Dulindra, > > What are the user stories that make this a requirement ? > > If we think from a user POV (if not already done) maybe we"ll be able to > capture some edge cases as well. > > +1. @Mushthaq, Can you share the user story for this ? > Thank you, > Shiro > > *Shiroshica Kulatilake | **Solutions Architect, **WSO2 Inc.* > *+94 776523867 <%2B94%20776523867> * > > On Mon, Oct 26, 2015 at 2:11 PM, Mushthaq Rumy <[email protected]> wrote: > >> Hi all, >> >> I'm going to implement a permission model for the GReg publisher which >> the scenario is somewhat similar to the permission model in the management >> console. >> >> There are some issues in the permission model of the management console. >> >> 1. The CRUD operation semantic is not well defined. >> Eg: A role which has *write* permission might not have *read* >> permission >> >> 2. A complex matrix grid of permission which causes user unfriendliness. >> >> I'm planning to fix these issues in the permission model for the GReg >> publisher. The UI wireframe and the flow of the model will be as follows. >> >> 1. The user will be able to navigate to the permission screen by clicking >> the *Permissions *tab on the top of the screen as shown below. >> >> [image: Inline image 2] >> >> 2. The user will be able to restrict the resource with *read only* >> permission to all the internal users by checking the *Public to internal >> users *option. >> >> [image: Inline image 1] >> >> 3. The user will be able to share the resource with *read only* >> permission to all the public users by clicking the *Public to everyone * >> option. >> >> [image: Inline image 2] >> >> 4. The user will be able to share the resource with other roles by >> checking the *Share with other roles *option, selecting the role to >> share and selecting the permission to give the selected role. >> >> [image: Inline image 3] >> [image: Inline image 3] >> >> 5. The user will be able to remove the added permissions by clicking the *x >> *link of a particular permission. >> >> Are there any improvements i can make to the above design. Appreciate >> your suggestions. >> >> Thanks & Regards, >> >> -- >> Mushthaq Rumy >> *Software Engineer* >> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194> >> Email : [email protected] >> WSO2, Inc.; http://wso2.com/ >> lean . enterprise . middleware. >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > -- Dulindra Wijethilake Senior Product Manager WSO2, Inc.; http://wso2.com lean.enterprise.middleware mobile- +94 71 820 3810
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
