Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom fields editable in the members portal #996

Open
jefft opened this issue Jan 12, 2024 · 3 comments
Open

Custom fields editable in the members portal #996

jefft opened this issue Jan 12, 2024 · 3 comments

Comments

@jefft
Copy link
Contributor

jefft commented Jan 12, 2024

Within the /members portal, Jethro allows users to edit their own basic details:
image

There are some custom fields that it would be nice if users could update themselves. WWCC and WWCC Expiry Date are potential examples. For this it would be nice if custom fields could be flagged as editable by their owner. Something like:

image

@alburyAJ
Copy link

Hi Jeff. I like the direction of this and it will streamline admin if members can see and in some cases edit specific data fields. However for us, the WWCC fields are managed by staff so that no member need be concerned that someone could pretend to have a WWCC or modify an expiry date. So, could we perhaps have two checkable options: 'Read-only by this member' and 'Self-editable by this member'.

@tbar0970
Copy link
Owner

Yep, good idea, although WWCC is probably not a good example (it needs to be verified with OCG before being treated as legit)

@alburyAJ
Copy link

Agreed. A better self-editable example might be (say) 'My hobbies and interests' - a support to congregational connections but not a legal requirement. That said, if a field like WWCC could be made 'Read-only by all members', this might (say) help a kid's-outreach team to identify potential recruits, or help a parent confirm that a kid's-church helper is registered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants