You want to build a private app that can create new custom objects. What scope would you need to give this private app access to?
- crm.objects.custom
- crm.schema.custom
- crm.schema.objects
- crm.objects.owners
Explanation: The correct answer is crm.schema.custom. When building a private app that needs to create new custom objects within a CRM system, granting access to the crm.schema.custom scope is necessary. This scope specifically pertains to the schema or structure of the CRM, including customizations such as custom object definitions. By assigning this scope to the private app, it gains permission to interact with and modify the schema of the CRM system, enabling it to create new custom objects according to predefined configurations or specifications. This level of access is essential for the app to dynamically generate and manage custom object types within the CRM, facilitating the extension and customization of the system to meet unique business requirements. The other options, such as crm.objects.custom or crm.schema.objects, do not specifically address the need for modifying the schema to create new custom objects, making them incorrect choices for granting access to a private app intended for this purpose. Additionally, crm.objects.owners is unrelated to creating custom objects and is instead related to managing ownership or permissions for existing CRM objects, further emphasizing the relevance of the crm.schema.custom scope for the specified task. Therefore, to enable a private app to create new custom objects, granting access to the crm.schema.custom scope is the correct and appropriate action.