Does ModX support multiuser group based accounts? Where say someone registers an account that company is a "company" account and then the creator of the account manually adds users to it. Members of this "group" can then view/edit content specific to them depending on any granular user permissions assigned by the group account creator?
Ultimately there would be many "Companies" and their group would need to be made during account creation.
-
MODX Staff
- 10,725 Posts
Sure, but for those specific requirements, you would need to script an add-on with the logic you want, perhaps by looking at the existing registration script that comes with the default installation.
I was just asked to implement something like this yesterday! I am thinking about creating user groups for each "company" account. One of the issues is that they find having a manager account and a web user account very confusing. I also do not need them to see any of the admin, just be able to manage user accounts and see access logs. It is at the bottom of the list. But when I get to it I will let you know what I end up doing.
DropboxUploader -- Upload files to a Dropbox account.
DIG -- Dynamic Image Generator
gus -- Google URL Shortener
makeQR -- Uses google chart api to make QR codes.
MODxTweeter -- Update your twitter status on publish.
I’m also working on something similar for an extranet (still far from finished). My solution involves custom tables: `firms` contains the company data and `web_users_attributes_extended` contains a foreign key containing the user’s firm id. I have two webuser groups that webusers can belong to: ’member’ and ’admin’; the later group can register staff members for their own firm and assign privileges via custom registration forms (privileges are specific to my application not modx, and are stored in another custom table and cross referenced with the websuer; they allow the firm admin to define granular access to other parts of the application to selected members). The administration system is handled by snippets on the front end for logged in users using modx documents for the views.
I think this approach makes sense when you have a custom set of privileges that relate to what your members do with your application.
