Suppose you have a very simple Native Mobile Application which allows users to see all the products a company distributes.
One possible requirement is that the same application is used by employees of the company (who have the authorization to add, update, or delete products, and change their prices), and will also be used by users who are interested in buying those products and are allowed just to navigate through the products list. Authorization is needed to update products, but not to navigate the product's catalog.
Another different requirement may be that authorization is needed for both cases, and the authorization for each action (navigate the products catalog and update the data) has different permissions related to it.
The following steps show you how to achieve this, regarding permissions in the application, and how to solve it using GAM.
Objects of the application:
- Product Transaction (Business Component)
- Dashboard1 which has the following item:
- WorkWithProduct (Work With object which lists all the products). By selecting one item of this list you can view the detail of the product; and update, or delete the product if desired. There is also the possibility of adding a new product by using the menu of this object.
Case 1. Insert, Update, Delete are restricted actions, but the list of products does not require authorization to execute
See How to: Permissions in SD applications, CRUD restricted
See How to: Permissions in SD applications, WW and CRUD restricted
GAM - Permissions
Full Control Permissions and inheritance
GAM Authorization Scenarios