See the open feature request: Option to save the Signature data (user,name, date) in a Tulip table
Signature storage and access are sensitive in regulated environments, which adds some complexity and creates issues with treating signature the same as other fields. Most notably, these signatures must be immutable. Right now there isn’t a mechanism to make a table record field immutable (like completions). This is the driving mechanism for the split of Completions and Tables, but is something we are looking to better unify in the coming year.