Missing table permission when saving a document
Business Central is telling you that your account may read the named table but may not create rows in it, so the record is refused before it is saved. This is a rights problem, not a data problem. An administrator has to assign a permission set that includes Insert on that table, for the company you are working in.
Every table access in Business Central is checked against the sum of the permission sets assigned to the user. Each permission set grants Read, Insert, Modify and Delete separately per table object, and each assignment can be limited to a single company. When the running code tries to create a record and none of the assigned sets grants Insert on that table in that company, the platform stops the operation and names the table and the missing permission type. The same check applies to background sessions, API calls and extension code, which run under an account of their own.
Define one permission set combination per role and assign that combination, rather than adding single sets when someone reports a block. Check a new role with Effective Permissions in a sandbox before rolling it out, and review assignments after every extension install or upgrade, because new tables ship with new permission sets. Keep in mind that a licence limit is not a permission problem: a Team Member licence restricts which documents may be created at all, and no permission set overrides that.
No. Assigning permission sets requires an administrator, normally someone with the SUPER permission set. A standard user can look at Effective Permissions but cannot change the assignment.
Usually one of three reasons: the session still holds the old permissions and needs a fresh sign-in, the assignment is limited to another company, or the user's licence does not entitle them to create that record type.