[Vtigercrm-developers] Has anyone setup or implemented restricted sharing?

[VaShaun Jones]

Well before I unsubscribe I wanted to say thanks.
On Apr 5, 2012, at 3:37 PM, Adam Heinz <amh at metricwise.net> wrote:

> Unsubscribe is at the bottom of the page:
> http://lists.vtigercrm.com/mailman/listinfo/vtigercrm-developers
> 
> On Thu, Apr 5, 2012 at 3:27 PM, VaShaun Jones <vashaun.jones at gmail.com> wrote:
>> Hi,
>> 
>> How do I unsubscribe from this list. Somehow I seem to be getting messages from this V-Tiger thing and it has no unsubscribe. Any help would be appreciated.
>> 
>> Thanks in advance,
>> VaShaun Jones
>> On Apr 5, 2012, at 12:20 PM, Adam Heinz <amh at metricwise.net> wrote:
>> 
>>> I was noodling around with something similar to this problem today and
>>> I discovered that if you're willing to modify the database outside of
>>> the admin ui, you CAN grant module permissions for edit view without
>>> granting save (which is currently useless, but has potential for
>>> create vs edit) and it looks like you can also grant module
>>> permissions for list view without granting detail view.
>>> Unfortunately, I am describing core permissions, not sharing rules.
>>> 
>>> Now, stock vtiger only has two sharing rules, read and write.  Read
>>> maps to edit view and save, write maps to list and detail views.  My
>>> custom build already runs with a third sharing type, delete.  I've
>>> attached a patch that shows how I've taken the hard-wired read/write
>>> functions and replaced with a more generic function that also supports
>>> delete.  Of special note is the section commented with // FIXME: Magic
>>> numbers.  (D'oh.)  There's no reason that we couldn't do away with the
>>> actionid to string mapping entirely and get extremely granular sharing
>>> permissions, which would allow Mark to do list-only sharing.
>>> 
>>> Looking at this from a different angle, I'm not sure what you gain by
>>> giving someone list view access without detail view.  I can customize
>>> my list filters from the user interface, so I can display everything
>>> available in detail view in list view.  There's no security benefit to
>>> granting one without the other.
>>> <sharing.patch>_______________________________________________
>>> http://www.vtiger.com/
>> 
>> 
>> _______________________________________________
>> http://www.vtiger.com/
> 
> _______________________________________________
> http://www.vtiger.com/