Open jefft opened 2 years ago
Related issue: https://github.com/tbar0970/jethro-pmm/issues/487
I second this. I am going through our (printed) church directory and notice that some people don't have all their details published. I was thinking more along the lines of a 'private' flag against phone, email and address.
I was thinking more along the lines of a 'private' flag against phone, email and address.
That's one more level of complexity :) I might be happy to share my home address with one group but only my email with another...
I was thinking more along the line of a blanket private flag and was only thinking in terms of the address book. This way around it could be an attribute of the group that says if 'private' information can be viewed by the group. But then my original idea was purely related to whether it appears in the address book (or other 'public' places).
I think I will raise a separate issue as my suggestion is at a slightly different angle.
Jethro's killer feature (IMO) is its ability to act as an address book, letting church members find contact details for each other. I think 'online church directory' functionality could be greatly enhanced by making 'consent to share' a per-person, rather than per-group.
The model Jethro currently supports is of a church-wide Church Directory. Users who have given their consent to share details are added to a Church Directory group that has the 'Share member details' flag set:
This 'church directory' model works, but has limitations:
'Consent to share' is fundamentally a per-person datum. I would like 'consent to share' to be a per person, per group flag set in the member portal:
or possibly also per-congregation:
The existing group 'Share member details' group flag should have its meaning altered from will share to could share:
Only groups with the repurposed 'Share member details' flag would appear in the 'Share with these groups' drop-down.