Permission API

The permission API exposes a number of methods to analyze the access rights of a given user. These methods assist extension developers to secure their resources. The ES extension model supports the following permission APIs:

Methods name	Description	Example
`hasAssetPermission`	This method is used to check specific asset type permissions.	hasAssetPermission(‘ASSET_CREATE’,’gadget’,session); hasAssetPermission(‘ASSET_CREATE’,’gadget’,tenantId,username); By default the `hasAssetPermission` method is executed taking into account the logged in user's session and tenantId. If you wish to check the asset type permission of specific user, you need to define the tenantId and username of the specific user.
`hasAppPermission`	This method is used to check permissions which are independent of the asset type. Example: Verify if you have permission to access the My Items page.	hasAppPermission(‘APP_MYITEMS’,session); hasAppPermission(‘APP_MYITEMS’,tenantId,username); By default the `hasAppPermission` method is executed taking into account the logged in user's session and tenantId. If you wish to check the permission for independent asset types of specific user, you need to define the tenantId and username of the specific user.
`hasAssetPagePermission`	This method is used to check the access permissions of a user for an asset specific page.	hasAssetPagePermission(‘gadget’,‘list’,tenantId,username);
`hasAssetAPIPermission`	This method is used to check access permissions of a user for an application specific page.	hasAssetAPIPermission(‘gadget’,‘assets’,tenantId,username);
`hasAppAPIPermission`	This method is used to check access permissions of a user for an asset specific API.	hasAppAPIPermission(‘asset’,tenantId,username);

Enterprise Store 2.0.0

Permission API

`hasAssetPermission`

`hasAppPermission`

`hasAssetPagePermission`

`hasAssetAPIPermission`

`hasAppAPIPermission`