Secondary Users: Access to modules that require a user account

#### Steps to reproduce the issue

1. Create a fully connected Jetpack site
2. Add a new admin user
3. Log in with your new admin user and go to `Jetpack->Settings`
4. Modules that require the **current user** to be connected, like "Downtime Monitoring" will be enabled.

#### What I expected

Modules that require the **current user** to be connected, like "Downtime Monitoring" should be disabled

#### What happened instead
"Downtime Monitoring" is enabled. The link to "Configure your notification settings" will not work.

**Screenshots**
After clicking the "Configure your notification settings" with a non-connected secondary user:

Reproduce the issue by creating a connected Jetpack site, adding an administrator, and checking Jetpack → Settings as that secondary user. Trace the access checks for account-dependent modules such as Downtime Monitoring; done means those modules are disabled for non-connected users and the notification-settings link is not exposed.

Written by the indexing model from the issue text.