While access to records in the table is controlled by user roles and settings defined in ACL access to records from artifacts like business rules, workflow, script includes relies on Application Access settings, which are defined in the table module.

For example, a user can access the record we created in the Booking Request table as long as the user has the proper role granted. In our case, x_8940_travel_book.user user role must be granted to all users who wish to access records stored in the Booking Request table. This is true for users and groups; however, server-side scripts like business rules, script includes, and workflows have application scope set for each artifact entity.

The application scope field shows which application scope an artifact belongs to. In such scenarios, the Application Access settings of the table come into the picture. These can be used to allow access to records stored in the table from all application scopes.

We can set the table records to be accessible from:

• All application scopes
• This application scope only (the scope the table is part of)