The verification whether some user can access an object (Web Panel, or Report) will be done automatically by GAM Security. So, the only functionalities that have sense to assign in this step are the ones related to actions, links or tabs.

Each of these items (actions, links or tabs) can have a functionality different from each other, or you can group many objects into one functionality. These is defined in its 'Security Functionalitiy Key'.  

WorkWithPlus will add the code in order to verify if some user can click in some action or link and will hide/disable the action when user doesn't have permission for it. This will be done the same way as it is done with WorkWithPlus Advanced Security: Security in Actions, Security in Links.

If the action invokes some Web Panel or a transaction in mode insert, update or delete and its value of 'Sec Functionality Key' is <default> WorkWithPlus will use GAM APIS in order to verify whether user has permission in order to access that object.

Also, WorkWithPlus will add the code in order to verify if some user can can visualize a Tab within the View object and will hide/disable the tab when user doesn't have permission for it.  This will be done the same way as it is done with WorkWithPlus Advanced Security, with the exception in the value <default>:

• When the property 'Security Functionality Key' of a tab is <default>, WorkWithPlus won't add security for that Tab.
• When the property 'Security Functionality Key' of a tab is any other value, WorkWithPlus will do the same thing that does for Tabs in  Advanced Security: Security in Tabs.

After this, you have to follow steps included in section Update Security Funcionalities . The first one is Update Security Objects Code.