Role based security in Axapta 2012

Based on a security role a user will get privileges associated with role, means no role has no privileges

In Axapta Role-based security is defined as per the structure of the business, in organization a user will get security roles based on their responsibility and their involvement in business process, Administrator is not involving every time if a user’s responsibilities change

 

·         Role a group of duties that are required by an end-user to do his/her job based on the end user's role in the organization, it is organized into a role hierarchy

• Process
• Duties
• Privileges
• User Interface Elements
• Tables and Fields
• SSRS Reports
• Service Operations

Once security role must assigned to all the users to access the Axapta, based on security roles that are assigned to user determine the duties that user can perform and depends on that limited interface user can view 

Administrator dose data security policy to access the data that the users in a role have access to, administrator save time in terms of not managing access separately for each user; for organization it is one time to define security roles, user can automatically assigned to roles as per business data. 

Process cycles

                Maintain ledger account

                Maintain bank related transaction

Duties are  a group of related privileges required to perform a task

                Maintain bank related transaction

                General deposit slips

Cancellation of Payment

Privileges is a group if related permissions that are required to perform a duty

Cancellation of Payment

 

Access levels

 

No Access - No Access to data

Read -          User can View Data

Update -       User can View and Edit Data

Create -        User can View, Edit and Create new Data

Correct -      User can View, Edit, Create new and correct date-effective

                     records without creating new records

Delete -        User can View, Edit, Create new and Delete Data