The purpose of application scoping is NOT to provide a way of tracking the user who developed an application. Application scoping does not store or display information about the user who created or modified an application or its artifacts. The purpose of application scoping is to provide a relationship between application artifacts, provide a namespace to prevent cross-application name collisions, and provide controls for how scripts from another scope can alter tables in a scoped application. References: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]

The Bar Chart and Pie Chart report types can be created by right-clicking on a column header in a table's list. These report types show how individual pieces of data relate to the whole using proportional bars or slices. You can also choose different aggregation methods such as count, sum, average, min, max, or percent. Reference: [Create reports from lists]

https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/GlideQuery/concept/GlideQueryGlobalAPI.html#GlideQueryAPI
https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/glideRecordScoped/concept/c_GlideRecordScopedAPI.html

"You must first select read access to grant any other API record operation." https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/reference/r_TableApplicationAccessFields.html The Application Access configuration fields control the access level for an application and its tables. The following Application Access configuration fields are not available if the Can read configuration field is not selected:
Can create. This field determines whether users can create records on the application tables.
Can update. This field determines whether users can update records on the application tables.
Can delete. This field determines whether users can delete records on the application tables.
These fields are not available because they depend on the Can read field, which determines whether users can view records on the application tables. If users cannot read records, they cannot create, update, or delete them either.
The following Application Access configuration fields are available regardless of the Can read configuration field:
All access to this table via web services. This field determines whether users can access the application tables using web services, such as REST or SOAP.
Allow configuration. This field determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes. Reference: Application Access, Certified Application Developer (CAD) Learning Path