Not sure if I’ve missed something in my configuration…:
– created a subdirectory subsite for a division that should not have access to the top level site or any of the other subdirectory sites.
– created a user for the new subsite two different ways with no success:
– first, created a user from the network dashboard, then added him as a user to the subsite (but not the root site). The system mailed his username and password to him, along with a link. The link goes to the root page login screen where the username/pw combination is accepted without error, but the page presented is the login page once again. Changing the address of the site to include the subsite allows the user in from this point, so the password was evidently accepted. However, this is a completely manual intervention to get access!
– second, I ‘invited’ a new user from the dashboard of the subsite as a new user. An email with a validation link was sent. The login screen appears and of course, there is no password to enter, so we get absolutely nowhere! This user is not on the Network list or any other subsite. Attempting to use the ‘lost password’ indicates the user is not known.
It is probably important to note that I’ve got the site locked down to be accessible/visible only to registered members, and those members are allowed access only to the sites they need. Up until this test, all users were included in the member list for the root site… so I suspect that’s where things are going wrong as these test users are not on that list. Because all the links seem to be directed to the root site, there is no way for the user to know where he’s supposed to go and the system is not redirecting behind the scenes.
Is there a workaround for this?
.
