I've just started my introduction to DNN, and using this user table with insert only records could be very useful for our business website.  Allowing our clients to place orders,( for printed materials), and giving them an upload column.  But the issue was preventing other users from that client, acidentally or intentional deleting those records.

Sorry this comment is not very technical but lets get this post off and running!

Actually, I think you're talking about something different - but I want that, too! I'm referring to a field that can only be set on insert. For instance, let's say you're using UDT to track current software issues. You assign it an issue ID, but you don't want anyone to change that in the future, so you'd like it to be read-only after being set for the first time.

I think you're more referring to custom permissions on a per-row basis. That is something else I'm being asked about, but any way that I can think about implementing it would just be a bear to maintain. Creating a row edit vs. UDT management permission wouldn't be hard, however. Heck, even an owner-edit permission wouldn't be that hard. The only problem with that is that only one person can edit the row (besides admins and UDT managers). I know that in my situation, groups of users will be wanting to edit different rows. They want each row to be edited based on the project they work on. This goes way beyond anything DNN can handle without writing your own rights management system. That just drives me crazy. I just wish Microsoft would've added qualifiers to go with permissions. That way, you could give more granular permissions. Anyway, I'm done, now

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com