# Hidden scopes crm.objects.emails.read / write needed for app

**URL:** <https://community.hubspot.com/t/hidden-scopes-crm-objects-emails-read-write-needed-for-app/149552>\
**Category:** APIs & Integrations\
**Tags:** email\
**Created:** [May 21, 2026, 5:05am UTC](https://community.hubspot.com/t/hidden-scopes-crm-objects-emails-read-write-needed-for-app/149552 "2026-05-21T05:05:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chief1901](https://avatars.discourse-cdn.com/v4/letter/c/3d9bf3/32.png) [@Chief1901](https://community.hubspot.com/u/Chief1901)\
**Post date:** [May 21, 2026, 5:05am UTC](https://community.hubspot.com/t/hidden-scopes-crm-objects-emails-read-write-needed-for-app/149552/1 "2026-05-21T05:05:07Z")

</div>

App Client ID: 110a69ea-0f55-44ae-8460-4c8b9684d5f7  
Problem: When my app calls GET /crm/v3/objects/emails, HubSpot returns HTTP 403 with category: MISSING\_SCOPES and lists three acceptable scopes in requiredGranularScopes:  
- crm.schemas.emails.read  
- crm.objects.emails.read  
- sales-email-read

The sales-email-read scope is silently dropped from OAuth grants (deprecated in Sep 2025 rollup). The two granular scopes are not selectable in my app’s Auth tab — they don’t  
appear in the scope picker dropdown despite the API requiring them. Other users have reported the same pattern with crm.objects.notes.\*. Please enable scope visibility for this app, or advise the correct alternative scope that grants access to /crm/v3/objects/emails.  
Tag: oauth-scopes

---

<div class="post-metadata">

**Author:** ![stassey](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stassey/32/36_2.png) [@stassey](https://community.hubspot.com/u/stassey)\
**Post date:** [May 21, 2026, 9:35pm UTC](https://community.hubspot.com/t/hidden-scopes-crm-objects-emails-read-write-needed-for-app/149552/2 "2026-05-21T21:35:38Z")

</div>

Hi @Chief1901,

Welcome to the Community!

It could be worth taking a look at the related community thread linked below to see if any of the workarounds there apply to your portal.

- [Need access to crm.objects.emails.\* scopes for the Engagement API](https://community.hubspot.com/t5/APIs-Integrations/Need-access-to-crm-objects-emails-scopes-for-the-Engagement-API/m-p/1172977)

The current scope requirements for the endpoint are also outlined in the [Activities | Email API guide](https://developers.hubspot.com/docs/api-reference/crm-emails-v3/guide).

I’d also like to tag in some of our Top Contributors to see if they’ve run into this scope visibility pattern before:

Hey @SteveHTM, @Anton, @evaldas -- Do you have any suggestions on this?

Thanks in advance!

Sam, Community Manager