User child functionality required and bookings linking

Permalink
Hi i'm running a 5.6 install of C5, i need to be able to create 'child users' of the 'parent user', these child users will inherit contact details and won't require a password or email as the parent will login, the 'child users' will only need to be created to be linked to the parent.

The reason which may explain better....

Site is for a nursery, parents register, they add their children to the profile and then they can select to add these children to a booking for a day or week.

The client can then see which children are booked in for that day.

I can do quite a bit of this with ProForms & ProEvents, but just cant find a clean way to make the child aspect work.

If anyone can help me please let me know asap!

Thanks

Ben

BHWW
 
JohntheFish replied on at Permalink Reply
JohntheFish
Why do children need to be users?
BHWW replied on at Permalink Reply
BHWW
Do you have a better suggestion, my thinking is that they need to be unique objects to allow you to assign attributes to them such as DOB, sex, name, medical info

And to allow you to report on the objects?
manup replied on at Permalink Reply
manup
Here are the steps

1. Create User Groups 'Teacher' and 'Children'

2. Install 'User Picker Attribute' and assign it to User Collection from Settings

3. Create a new user attribute based on 'User Picker Attribute' say 'Parent User', Let it list down users from 'Teacher' User group.

4. Front end needs programming for filter childs based on parent.

5. Teacher Register, and he/she can add sub users under logged in user.

$ui->setAttribute('parent_user', 10);


ALSO: ProForms & ProEvents plugins cannot help in such requirements.
BHWW replied on at Permalink Reply
BHWW
Thank you, I can see where you are going, but each child user would still need a unique email and username and password??

Maybe 'users; is the wrong term, maybe they should be child objects under a user?

But you'd want to be able to access the child objects seperatly too, a bit like the auto nav, you can specify, list pages under parent, list pages at second level, list parent pages, etc....
manup replied on at Permalink Reply
manup
but each child user would still need a unique email and username and password?? [ YES, child user can still login ]

Maybe 'users; is the wrong term, maybe they should be child objects under a user? [ YES ]

But you'd want to be able to access the child objects seperatly too, a bit like the auto nav, you can specify, list pages under parent, list pages at second level, list parent pages, etc.... [ YES, It requires a Special Filtering Queries ]
BHWW replied on at Permalink Reply
BHWW
So PM me your quote :)