The one thing to bear in mind is that MODx requires the user permissions to be set before it allows them to access the various parts of the manager. If these permissions are not set then the system will not allow the user access to the secured sections of the manager.
If you should try to overide the permissions then we have no way of telling who is allowed to do what. That’s why I think having an alias account with the proper permissions enabled can be used as means for grouping your Mambo users.
A Mambo Connector plugin can be used to authenticate Mambo users and mapping those user accounts to an existing manager account. These MODx accounts are used as an alias to Mambo users to provide things like role and group assignments. In other words you can use one manager account with multiple Mambo user accounts.
example:
Mambo User MODx User
-------------------------------
Mary -> MamboUserDemo1
Tom -> MamboUserDemo1
Kim -> MamboUserDemo1
Jane -> MamboUserDemo2
Paul -> MamboUserDemo2
Whenever Mary, Tom or Kim logs into the manager they will have the same access rights as that of the MamboUserDemo1 account while Jane and Paul will have the access rights as that of MamboUserDemo2.
The only problem here is that you’ll not be able to track who did what inside the Audit trail, because the system will not show the Mambo user (Mary) but the MODx user name (MamboUserDemo1).