Ladroge, There is a "SecurityPermission" entity which describes granular security permissions, which could be for a particular page or a particular service.
SecurityPermission is a two part string, separated by an "_". The first part specifies the application, the second part the operation allowed. Thus, you could have a permission like " CATALOG_CREATE" which means that the user with this permission can create information in the catalog manager. Some permissions end in _ADMIN, such as CATALOG_ADMIN. Those permissions automatically have the right to every operation in the application. Individual security permissions are grouped together into groups with the "SecurityPermissionGroup" entity which groups these permissions together. For example, you can create a specific sets of permissions for customer service representatives who can view customer information, enter orders, but not make purchase orders or access internal manufacturing, accounting, or payroll information and functions. Each SecurityPermissionGroup is associated with a UserLogin. A Party, which can be a Person or a PartyGroup (ie, organization) can be associated with multiple UserLogins. Thus, a Person can have some logins with more permission and some with less, which can be helpful with larger customers (or larger families, for that matter.) I hope it might be helpful for you. On 6/10/08, ladroge <[EMAIL PROTECTED]> wrote: > > > Hi > I want to create some permission rules on my catalogs. In the application > we > have some permission such as: ACCOUNT_ADMIN, FULL_ADMIN, > > How can i create a specific permission which can give priority on catalogs > or product for user; > > Thanks > -- > View this message in context: > http://www.nabble.com/How-to-create-Permission-tp17751376p17751376.html > Sent from the OFBiz - User mailing list archive at Nabble.com. > > -- Anil Soni Software Engineer Amicon Technologies Private Limited 6th Floor - Unique Tower, Behind Patel Patrol Pump, Goregaon (W), Mumbai MH Contact no.- +91-9892271357
