Clint Kaul
My feedback
35 results found
-
69 votesClint Kaul
supported this idea
·
-
29 votesClint Kaul
supported this idea
·
-
36 votesClint Kaul
supported this idea
·
-
32 votesClint Kaul
supported this idea
·
-
73 votesClint Kaul
supported this idea
·
-
66 votesClint Kaul
supported this idea
·
-
208 votesClint Kaul
supported this idea
·
-
112 votes
We started working on providing members ability to stop their own membership. Stay tuned for updates!
Clint Kaul
supported this idea
·
-
56 votesClint Kaul
supported this idea
·
-
5 votesClint Kaul
supported this idea
·
-
152 votesClint Kaul
supported this idea
·
-
123 votesClint Kaul
supported this idea
·
-
10 votesClint Kaul
supported this idea
·
-
4 votesClint Kaul
supported this idea
·
-
7 votes
An error occurred while saving the comment
I'm actually in the opposite situation but I could make either solution work. We have family (parent/children) memberships. The parent has the common contact info (USmail, phone, email, ...) while the children (and parent) would have member specific details (# activities, date completed, ...).
Currently if the parent goes to add a child, they have to enter all sorts of contact info (USmail, ...) which we ignore. If they were at least pre-filled from the parent (bundle admin) that would help. I know most web browsers have auto-fill which reduces the labor.
Ideally? it would be nice to tag (in the back-end) each common field and membership field indicating whether it was shown for bundle admin, bundle member or both. Perhaps another tag (in the back-end) indicating whether a bundle member field is auto-filled from the bundle admin or not?