Permission error when posting or saving a record
Business Central stopped the operation because your user lacks the permission listed in the brackets, here Insert on TableData 21 Cust. Ledger Entry from the Base Application. The bracket is the useful part: it names the object type, object ID, object name, missing permission and the extension that owns the object, which is exactly what is needed to grant it. Permission sets and licences can only be changed by an administrator, so in most cases you have to pass this message on rather than fix it yourself.
On every read, insert, modify or delete, the platform checks your effective permissions, which are the union of the permission sets assigned to your user, narrowed by the licence or plan attached to your account and by any security filters. If one required permission is missing, the operation is aborted with this message and the missing item is spelled out in brackets. Note that the failing table is frequently one you never open directly: posting a document writes to ledger and entry tables behind the scenes, so the permission gap surfaces on an object that has no visible page in your role centre.
Build access around role-based permission sets that follow whole business processes rather than patching individual tables when a user complains, because a posting routine touches dozens of tables and fixing them one by one produces a permanent trickle of errors. Test each role with a real non-administrator test user before rolling it out, since administrators and SUPER users never see these messages and a sandbox with SUPER assigned hides the problem entirely. Remember that security filters and the licence level can block an action even when the permission set looks correct, so check all three layers before concluding that a permission set is at fault.
TableData means the data stored in a table, 21 is the table ID and Cust. Ledger Entry is its name. The word that follows is the permission type that is missing: Read, Insert, Modify or Delete. The name after the colon is the extension that owns the object.
Usually not. Assigning permission sets in Business Central and licences in Microsoft 365 requires an administrator. The fastest route is to send the exact text in the brackets to your administrator or partner.