# Permission set extension object
> APPLIES TO: Business Central 2021 release wave 1 (v18.0) and later
The permission set extension object in Business Central adds permissions to an existing permission set defined in AL. A permission set extension object can't remove permissions from an existing permission set; it can only add permissions. If you, for example, add an extension to Business Central, you can use permission set extension objects to grant permissions to the objects in your extension. This means that the admin of Business Central doesn't have to assign extra permission sets to the users, because that automatically happens when the extension is installed, and the permissions go away if the extension is uninstalled.
Learn more about which permissions can be assigned to objects in devenv-permissions-on-database-objects.
## Designing with cautiousness
If a permission set is extended through AL, that extension makes additive changes to the permission set. This means that an extension can provide elevated privileges to an otherwise limited set of permissions. Building permission sets that can be extended must be done carefully with this in mind.
A best practice when creating an application with permission set extensions is to ensure that they only add permissions for objects, which are part of the application. This is because an administrator might not realize, or expect, that installing a new application might also grant elevated privileges. This design pattern minimizes the possibility of the permission set extension impacting any functionality beyond the intended application. This keeps the permission changes predictable and targeted.
## Snippet support
Typing the shortcut tpermissionsetextension creates the basic layout for a permission set extension object when using the AL Language extension for Microsoft Dynamics 365 Business Central in Visual Studio Code.
> TIP
> Use Ctrl+Space to trigger IntelliSense and get assistance on code completion, parameter info, quick info, and member lists. For more information about snippets, see Syntax and snippets<devenv-syntax>.
## Permission set example
The following permission set extension example extends the `Sales Person` devenv-permissionset-object#permission-set-example by adding direct insert and delete permissions to the Currency table data.
```al
permissionsetextension 50140 "Extended Sales Doc" extends "Sales Person"
{​
    Permissions =​ tabledata Currency = ID;
}
```
## Related information
Developing extensions<devenv-dev-overview>
AL development environment<devenv-reference-overview>
Entitlements and permission set overview<devenv-entitlements-and-permissionsets-overview>
Permission set object<devenv-permissionset-object>
devenv-permissions-on-database-objects
properties/devenv-assignable-property
properties/devenv-permissions-property

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-permissionset-ext-object, 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. https://jonas-paprotka.de/docs/dev-itpro/developer/devenv-permissionset-ext-object/
