(An application developer needs to ensure that no other private application scopes can create records...

Application Access on a table defines cross-scope behavior at the table boundary. To ensure that no other application scope can create records on the application’s data tables, the table must be restricted so that only the owning scope can access it. Setting Accessible from to This application scope only enforces that boundary by preventing other scoped applications from accessing the table, including record creation. This is exactly what the requirement describes: blocking other private scopes from creating records on the table. The “All application scopes” option is the opposite of what you want because it opens cross-scope access, and then trying to selectively block “Can create” still leaves broader exposure and is not aligned with the stated goal. Creating ACLs to block other scopes is also not the correct approach for cross-scope isolation because ACLs primarily control user and role access, while cross-scope access is governed by Application Access and cross-scope rules. Disabling “Allow access to this table via web services” is about API/web service exposure, not about other application scopes creating records through normal platform access.