update a record, do a read, and as part of the read, return if you canUpdate boolean for the logged in user.
delete a record, do a read, and as part of the read, return if you canDelete boolean for the logged in user.
so canUpdaet, and canDelete would be non-real fields on the model/table, that take in some code like, xyz role can see the record, and maybe xyz user is the logged in user
Really this should be done on every record, so the form's can also respect this.
Imagine a readmany on user, and you can edit your use but no one else.
So when you want to
so canUpdaet, and canDelete would be non-real fields on the model/table, that take in some code like, xyz role can see the record, and maybe xyz user is the logged in user