I recall encountering this issue before. If you think about it, it does makes sense: since the connector relies on an existing identity, the account must be aggregated before user-level access can be requested. As a workaround, you can use the ACTION tab to assign the user level as an admin.