Ah, in this thread your use-case is a bit clearer (but I actually saw your later post first).
In this kind of case, I’d recommend setting up a “form template” where the right kind of data is put into temporary fields. (See documentation https://tiddlywiki.com/#ActionCreateTiddlerWidget ) When all the data is drafted in this temporary way, a button action can check that all the values are within expected range, and then commit that data, if all looks complete, into a new tiddler (maybe even one that does not show an edit button, or one that doesn’t even get opened in the story river, but just quietly contributes to the data being archived in your project).
What kind of internal system do you have? If you’re running on node.js you may be especially interested in the MWS developments (Multi Wiki Server: Authentication and Authorization) that would more powerfully allow some people certain kinds of limited access, while other users (an administrator of the TiddlyWiki “app” you’re developing) can do more high-level things…