when logged in on the main site as 'admin', I had to log in again to each of your sub-sites.
I was confused too about that, I assume it's a security feature, since this is an internal server service of onTheGoSystems.
I will consult about this with the Systems manager, but he will be back only Monday.
I have set it as subdomains, yes. I should be able to ask to change that, if it is necessary, although, this should not be a problem I think.
Do you think there's a possibility that the Codex is wrong or that the WordPress coding hasn't been set up as intended?
That is what I see on all my MultiSites, and I never heard or experienced that users get added as "potential" users with actual rights on other sites, if they are added to one site in an MS install.
That is why I was quite surprised when you showed me the Codex - but of course I believed what was written there and did not doubt, that I must have done a mistake on my first test.
Actually, does your Site behave like the Codex illustrates?
Are users automatically Subscribers even if not explicitly added as such manually to other sites?
In my opinion that is also expected, I don't want users of Site A to have a real role on Site B, that might not even be related at all to Site A.
I would even be concerned if that would happen automatically.
Additionally, several external Posts actually state that new users are NOT subscribers automatically on other Sites of the network:
hidden link
hidden link
And even better (or worse) the Plugins that allow this, clearly state:
Running a WordPress network? You no longer need to manually add new users to each of your sites.
hidden link
I think, with this I am secure enough to state (I know it's bold) that the Codex is wrong.
Didi you know that anyone logged in to WordPress can actually edit the Codex?
It's not a "donkey safe" Documentation.
It's a "user driven" Documentation, and errors do sneak in, I reported a few in past myself.
If the Codex is wrong, which I highly suspect by now, everything works just as expected.
Toolset can not change that, and does also not change the Network behavior, which means, we would not change the default role.
What would be possible is that Access would not recognize the role correctly, but as said, to me it seems, this is a Codex issue and not a Plugin BUG.
At least all tests actually speak for this, because even if you disable Access, the behavior does NOT change, which means, it's not an Access BUG, do you agree?
If so, I will ask around in my Team, and eventually file a WordPress Support Forum report, where other WordPress users could share their experience and finally, we could update the Codex.
Is there something in the meantime that Toolset can provide as a workaround which would give a default role of Subscriber to Users on non primary sites?
No, but why don't you use one of those Plugins, that actually offer exactly that feature?
I am quite sure, after the issue disappears.
You are free to test them on our Server as well, I will keep that site online until we are done here.
Eventually we will learn a lot here, and contribute to the WordPress community!