{"title":"Permissions on objects","url":"https://jonas-paprotka.de/docs/dev-itpro/developer/devenv-permissions-on-database-objects/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-permissions-on-database-objects, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-permissions-on-database-objects","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"This article provides an overview of permissions on objects in Business Central.","date":"2025-06-02","meta":{"topic":"concept-article"},"outline":[{"level":2,"title":"Permissions","slug":"permissions","at":116,"chars":2658},{"level":3,"title":"Permissions on objects","slug":"permissions-on-objects","at":1274,"chars":1500},{"level":4,"title":"Wildcard","slug":"wildcard","at":2319,"chars":455},{"level":2,"title":"Example","slug":"example","at":2774,"chars":564},{"level":2,"title":"Related information","slug":"related-information","at":3338,"chars":242}],"text":"This article provides an overview of permissions on objects such as tables, pages, and reports in Business Central.\n## Permissions\nIf you're granted permission to read a page, then you can open the page and view the data that it displays. If, however, you don't have write permission, you aren't allowed to enter data into that page.\nSometimes, when you open a page it displays information from several tables. To access the page, you must have permission to view all the data displayed by the page. You might not have permission to read directly from all the tables that the page uses. In such a case, you must have indirect permission to read from these tables. Having indirect permission to a table means you can't directly open or read data from the table itself. Instead, you can only view the table's data when it's displayed through another object (like a page or report) that you have direct permission to access. The data is accessible only \"indirectly\" through these intermediary objects.\nBusiness Central has many standard predefined security permission sets. You can use these permission sets as defined or you can change a permission set to suit your particular needs. You can also create your own permission sets and assign them the permissions that you want.\n### Permissions on objects\nThe following table describes the permissions that can be assigned for specific objects. When assigning permissions by using the object types devenv-permissionset-object and PermissionSet extension object<devenv-permissionset-ext-object> these permissions have been shortened. The table illustrates the abbreviations used.\nPermissions on tabledata are specified with the following abbreviations:\nPermission|Description|Abbreviation in AL\nRead|You can read data.|R for direct read access, r for indirect read access.\nInsert|You can insert data.|I for direct insert permission, i for indirect insert permission.\nModify|You can modify data.|M for direct modify permission, m for indirect modify permission.\nDelete|You can delete data.|D for direct delete permission, d for indirect delete permission.\nPermissions on all objects are specified with the following abbreviations:\nPermission|Description|Abbreviation in AL\nExecute|You can run this object.|X for direct execute permissions, x for indirect execute permissions.\n#### Wildcard\nThe wildcard `*` can be used as a shortcut to assign multiple permissions at a time, such as:\n```al\nPermissions = codeunit * = X;\n```\n> IMPORTANT\n> The wildcard must be used with caution, because when it's used in a permission set it grants the permission to all objects of that type across all permissions. If a permission set with a wildcard is included in an entitlement, it only covers the objects of that type in the current extension.\n## Example\nAll of the permissions illustrated above can be combined into a group of permissions for any given object. For example:\n```al\n...\nPermissions =\n    tabledata Customer = RIMD,        // Full access\n    tabledata \"Payment Terms\" = RMD,  // Full read, modify, and delete access - no insert\n    tabledata Currency = rimd,        // Full indirect access\n    tabledata \"Sales Header\" = RIM,   // full read, insert, and modify access - no delete\n    tabledata \"Sales Line\" = RIMD,    // Full access\n    report \"Sales Statistics\" = X;    // Full access\n...\n```\n## Related information\nGet started with AL<devenv-get-started>\nEntitlements and permission set overview<devenv-entitlements-and-permissionsets-overview>\nPermission set object<devenv-permissionset-object>\ndevenv-permissions-on-database-objects"}