improve administrability of permissions
Ticket
+issues
Connectipedia lost a week+ of registrations and a number of Organization submissions because the permissions weren't set right. It's way too easy to make this kindof mistake.
+solution
two ideas come to mind:
- overview - a screen that lets you see & perhaps edit lots of them at once (see expose card metadata in cards and implement operations on groups of cards)
- implement notification system - send email to site owners when especially form posts are denied (possibly views as well)
revision history on permissions would be useful in these situations as well, and general notifications, in combo admistratiors could be appraised of all permission changes.
I suspect the biggest improvements here will come with pattern cards. wql for permissions would help (I think that's ticketed). Yup, in expose card metadata in cards.
Permissions will actually be fully in cards. The metadata is only relevant if those cards hinge on a WQL solution, which we should design. If, for example, we accomplished some of the metadata as a virtual card, you could only access them in wql with append/prepend.
--Ethan McCutchen.....Tue May 04 15:32:43 -0700 2010
close? (as duplicate of setting-ize permissions)
--John Abbe.....Wed Feb 16 12:03:59 -0800 2011
yeah, I think so. I mean, there will be some semi-separate work in reworking config pages and stuff, but that could easily be wrapped in with the settingize ticket, no?
--Ethan McCutchen.....Wed Feb 16 12:10:28 -0800 2011