Can network administrators manually associate Worksite users to the correct Employer network?

[Mark Messinger]

Users can become associated to a Worksite network merely by location. When the Worksite's location is the user's destination - voila! - the user is part of that Worksite network. Do I pretty much have that correct?

But, this seems to present a problem, particularly when Worksites are children of one or more Employer networks. It seems possible for users to become associated to the Worksite, but not to the correct parent Employer network.

As has been noted in other posts to this forum, this is causing confusion. Users assume they are associated with both the Worksite and the parent Employer network. But they are not.

There seems to be no way (in the iCarpool system) for a user who becomes associated with a Worksite network to be presented with a list of parent Employer networks, from which the user could then select and possibly (depending on the means of associating with that Employer network) eventually be made a member of that parent Employer network.

Is there any way for a network administrator have found to pro-actively identify users who are associated with Worksite networks - those who are not associated with Employer networks - in order to take steps which would eventually get that user associated with an Employer network, too?

I'm particularly interested in hearing from any network administrators who actually have experience in executing a process which found Worksite users and got them connected to the correct Employer networks.

[Tracy Ellis]

Yes. the RNA can go in to the users account and associate them with the network.  I have done that many times, I know Kathy King in Bend does that too.

What it entails is going in to the users account.

Find the network to join and submit a request to join

RNA receives a system generated email with a passcode (this is often forwarded to the user to complete the process, but frankly, it is just easier for the RNA to complete).

Then I go back to the users account. Click on Pending Networks, enter the passcode, and they are connected.

 

This seems to be the simplest way.  Of course, I'm worried that as the number of users increase, that will become too onerous a task.

 

Tracy

[Mark Messinger]

Thanks, Tracy, for the speedy reply.

But I'm not clear on one point.

If the Worksite network is associated with more than one Employer network, would you first email the user and ask them, "Are you an employee of Company A or Company B?"

. . . I think I need to fill out the Feedback Log. Can you imagine a system enhancement that allowed the user to self-identify as an employee of one of the parent Employer networks, then caused a notice to be sent to the contact for that Employer network?

[Tracy Ellis]

That has not ever been an issue for me. (Nor do I envision it becomming an issue). All of our employer partners are entered as worksites - then as I'm working with them setting up networks we can move their employees to the network.

I certainly like the idea of an easier way for a user to become associated with their employer network.