If we were to build an intranet with Umbraco used for things like News articles, bulletin board items and so on, the number of different people who would potentially need to edit documents could be huge (thousands).
Could Umbraco handle this (interfacing with Active Directory in some way to authenticate users)? Or is this a non-starter?
If so, another possibility is a small number of logins, but extra user information passed with the login and stored with the documents so that the 'editor' can be seen in the document audit trail.
The reason I became nervous was looking at the option to set permissions on a content node : if that had to build a table of checkboxes for thousands of users, that could slow or even kill the system (is my guess!).
To be honest, that sounds like a huge amount of work to allow members to edit what could be complex documents with many tabs and properties which users can do out of the box.
I guess Umbraco is off the table.
Essentially, it is designed for a small numbers of users to work on a site and where anyone can edit anyone else's documents...much as I like Umbraco, that doesn't seem a very modern scenario for a CMS.
Tim, I think you can try to use Users, but for easier persmission settings, try to add some events and change settings on user cretion event or some other event. Than you won't need to manage permissions.
Not sure what you mean. But we would have thousands of users (hopefully automatically authenticated by intergating with Active Directory), which was my issue : would this make the system slow and unsuable
Very large number of editors - possible?
If we were to build an intranet with Umbraco used for things like News articles, bulletin board items and so on, the number of different people who would potentially need to edit documents could be huge (thousands).
Could Umbraco handle this (interfacing with Active Directory in some way to authenticate users)? Or is this a non-starter?
If so, another possibility is a small number of logins, but extra user information passed with the login and stored with the documents so that the 'editor' can be seen in the document audit trail.
The reason I became nervous was looking at the option to set permissions on a content node : if that had to build a table of checkboxes for thousands of users, that could slow or even kill the system (is my guess!).
I appreciate any advice!
Hi Tim,
I think you are right, and in performance it can be slow. You can use Users one by one to set permissions.
Maybe it's better to use members for this?
Thanks,
Alex
Members would be fine, but they need to be able to edit content documents and I don't believe members can do this?
Tim, you have to write new pages for it, with custom code.
Do you mean new controllers and views?
But would they be able to use the Umbraco back-office html forms and controls for input?
Yes, new controllers and views.
It's not easy to use Umbraco backoffice for members.
To be honest, that sounds like a huge amount of work to allow members to edit what could be complex documents with many tabs and properties which users can do out of the box.
I guess Umbraco is off the table.
Essentially, it is designed for a small numbers of users to work on a site and where anyone can edit anyone else's documents...much as I like Umbraco, that doesn't seem a very modern scenario for a CMS.
Just my opinion!
Tim, I think you can try to use Users, but for easier persmission settings, try to add some events and change settings on user cretion event or some other event. Than you won't need to manage permissions.
What do you think about that?
Not sure what you mean. But we would have thousands of users (hopefully automatically authenticated by intergating with Active Directory), which was my issue : would this make the system slow and unsuable
is working on a reply...