# Permissions
# Old vs. New
Permissions for all API endpoints was introduced in the 0.4.0 release of the Lynx API. These permissions will replace all other permissions in a future release. These new permissions have a structure looking a lot like the endpoint paths for most actions.
The older permissions still control what a user can see and do in the AAM Web interface as well as how the old Android app looks.
# Structure (new)
The permissions are divided into groups depending on the resource. Almost all groups have one permission for every type of request that can be done. The only difference is that the creation and deletion of object are bundled into the same permission.
Most of the actions that involves an installation have two different permissions. One for assigned installations and one for all installations in the organization tree.
# All
Permissions ending in "all" means that the account are able to do the action on all installations that can be accessed in the organization tree. This means that all installations in all organizations of the user as well ass all child organizations and their children etc.
# Assigned
Permissions ending in "assigned" means that the account are able to do the action using an installations that has been assigned to the user.
# Reference list
The link below provides a downloadable spreadsheet with all new permissions.