@CLee 1176405 shakopee Thank you for submitting your question to our Community. I have some questions about this workflow:

Do those students all need to see it so any one of them could submit a ticket for it?

Do you want agents to see who is in a family so they don’t issue more than one per family?

Do you need to organize the distribution to families?

Do those students all need to see it so any one of them could submit a ticket for it?

• Ideally yes each member would be able to see to open a ticket, though we could get around this by just having a general MiFi issue.

Do you want agents to see who is in a family so they don’t issue more than one per family?

• Ability to verify only one being used per family and for collection at end of the year if their are siblings in lower grade we don’t collect upon graduation.

Do you need to organize the distribution to families?

• These are on a case by case so distribution is relatively simple.
• This is work flow under old helpdesk
  Request completed by admin / counselor with form attached to ticket.
  Device assigned to all students in family
  Device sent to level 1 tech to issue to oldest sibling to take home.
  End of year pull report of MiFis with only one assigned user and see if they are graduating to collect device.

So I spoke with some of my CS team, and here are some ideas @NBurke_iiQ and Ashley Holley came up with:

1. Custom field, noting that it is a family device, and then list out the other students within the family.
2. Add each additional student as a follower of the asset.
3. What about linking that MiFi asset to all of the family members assets and then having a view of linked MiFi? 

There is not a clean solution for this at the moment since our assets can only be assigned to 1 user at a time. Here is an idea to upvote about assigning a device to multiple users: