Can administrators ID Worksite users not associated with an Employer network?

[Mark Messinger]

How are administrators identifying users who are associated with Worksite networks but not the Organization/ Employer networks which are parents to that Worksite?

Sometimes, Worksite networks are created with no Organization/Employer parent. Users can become associated with the Worksite but, of course, they cannot self-identify their employer (there's no Employer network).

But, what happens if, at some later date, an Organization/Employer network is created and associated as a parent to the existing Worksite network. Are current Worksite network users then presented with an opportunity to select that employer as theirs?

This is why I ask my question. How can administrators identify users already associated with a Worksite, but not to the correct Employer network?

I have one more question.

Imagine a multi-employer worksite with a Worksite network. One of the employers has an Employer network established and associated as a parent to the Worksite network. But another employer at the same worksite does not have an Employer network. If an employee of this second employer associates with the Worksite, can that employee choose to associate with no Employer network?

Thanks.

[Tracy Ellis]

If there are multiple employers at one worksite, then that might be somewhat problematic.  Also, I have noticed that if someone registers in the database using their employer email address, THEN an employer network is created AFTER they have registered, they are not automatically associated with that network.  This is a flaw in the system and should be fixed.

I do have many employer worksites and have created employer network.  I then go in and see if the same amount of registrants are in both the employer network and the worksite.  IF there are more registrants in the workplace network, then I determine who is not in the employer network and I associate them with the network. 

This is a headache, but it is the only way I know of doing it.  Again, mulitple employers at one location - don't know the answer.  My worksite networks are set up as indivdiual employees.

 

But that does bring up a question I have.  Let's say two employers are at 175 W Broadway.  How would I set up that worksite network if there is no building name or some such associated with that location?  And what if one employer registers and has a network set up at that location, then some time later another employer at the same location signs up?

[Mark Messinger]

Thank you, Tracy, for your reply.

You wrote, " then I determine who is not in the employer network and I associate them with the network."

How is do you go about determining who among the Worksite users are not in the correct employer network?

I'm hoping to find a solution that would be useful for multi-employer Worksite networks. Some of the Worksite users might have no employer network to be associated with, and other users might need to be associated with an employer network.

Since Worksite networks are specifically designed to permit multiple employer relationships, I'm not clear as to how the system can automatically associate users in the Worksite to an Employer network. It seems the best that could be done would be some mechanism to allow an administrator to view all users already associated to the Worksite and then only select those users who work for the employer who now has an Employer network as a parent to the Worksite network. But, that sounds like a worthy enhancement request for iCarpool.

[Mark Messinger]

Tracy, you asked the question starting, " Let's say two employers are at 175 W Broadway. . ."

Are you asking what name you should assign to the Worksite? I agree, that's a problem with Worksite networks. The assumption seems to be system users will self-identify the location and thereby select the correct Worksite network. If there is no name for that location that users would recognize, it seems to undermine the idea of making it possible for users to self-select the Worksite they need.

What about if you were to create a separate Worksite network for each employer at that same location and incorporate the employer's name into the name you give to the Worksite? The manual Chapter 2: Creating Your Network reads, "The recommended naming convention is ORGANIZATION–WORKSITE NAME."

It seems to be your habit to set up Worksite type of networks, instead of Organization/Employer networks. When you wrote, "what if one employer registers and has a network set up at that location, then some time later another employer at the same location signs up?" what is the type of network the employers have, at that location?

If the first employer has a Worksite type of network, and then a second employer later is added to the same building, I guess you would create a second Worksite network. You would be careful to name these two Worksite networks in such a way as to include the employer name.

But, I'm not sure how you would remove some of the new employer's users from the original Worksite network and place them in the correct new Worksite network.

[Tracy Ellis]

How I determine who is and who is not in the networks is time consuming.  It requires me to run a report of users in the worksite, run a report of users in the network.  Then I determine who is in the worksite that is not in the network. It is not an elegant solution by any means.  I find that a lot of things we want to do with iCarpool are not easy. We have to hit it with a hammer rather than finesse it.  C'est la vie.

 

BTW, I name all of my worksites after the employer name.  I had forgotten that a drop down menu appears with worksite names for the user to self select.  I'm not too worried about the worksites. 

 

And I am not not creating networks in favor of worksites.  I am creating networks for my ERH employers. However, I find that in reality, some things do not work as well as in theory.  If you tell a user they need to be in the network, then they go to their networks page and see the worksite with their employer's name, they are going to believe they are in the network.  THAT is a problem.  People that feel they have to jump through too many hoops are going to say screw it.

 

[Mark Messinger]

Thank you, again.

Yes, running two reports and comparing the results, then attempting to figure out what Worksite users ought to be placed into the Employer network does sound like a hassle.

If both the Employer and Worksite network are created at the same time (assuming there are other reasons to have both types of networks, in the first place), then users who self-associate via the Worksite can choose from the list of parent Employer networks. And the administrator for the Employer network can enroll users via the means normally available for that type of network (Email domain, Import accounts, Administrator approval, Passcode, or Proxy registration).

That leaves another question of mine un-answered. That question seems to have to do with the drop down menu, which allows Worksite network users to self-select the employer.

Imagine a multi-employer worksite with a Worksite network. One of the employers has an Employer network established and associated as a parent to the Worksite network. But another employer at the same worksite does not have an Employer network. If an employee of this second employer associates with the Worksite, can that employee choose to associate with no Employer network?

I think it's possible for Worksite users to disregard that drop-down list, thereby associating themselves with no Employer network.

Hopefully, someone will stop me, if their experience indicates this is not correct.

[Tracy Ellis]

I think you may be confused. There is no way for a user to self select from a drop down menu to be associated with an employer network.

 

There is only one way to do that. Go to my networks and search for yrou employer then click join, using one of the three ways.  AGain, as I mentioned, if a person sees their employer worksite in their networks, they will assume they are in the employer network.

 

 

[Mark Messinger]

Um, I do believe it's possible for users, when they select a Worksite, to also select from a drop-down list the Employer network which is a parent to that Worksite network.

Do I have that wrong?

[Tracy Ellis]

yes. you have that wrong