# Better description for a Developer Seat

**URL:** <https://community.hubspot.com/t/better-description-for-a-developer-seat/141400>\
**Category:** Account & Settings\
**Tags:** developer, enterprise\
**Created:** [October 21, 2025, 10:20pm UTC](https://community.hubspot.com/t/better-description-for-a-developer-seat/141400 "2025-10-21T22:20:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![clvtross](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/clvtross/32/92090_2.png) [@clvtross](https://community.hubspot.com/u/clvtross)\
**Post date:** [October 21, 2025, 10:20pm UTC](https://community.hubspot.com/t/better-description-for-a-developer-seat/141400/1 "2025-10-21T22:20:22Z")

</div>

Good afternoon. I’m looking to gather detailed information about the Developer seat in HubSpot, specifically regarding its permissions and any other relevant capabilities. I’d like to share this with other IT personnel to ensure they understand the scope and functionality of this seat.

I believe that such information would benefit conversations regarding all seat types, which I am aware now incur a cost. Could you help clarify what access or tools are included with the Developer seat?

---

<div class="post-metadata">

**Author:** ![STierney](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stierney/32/186066_2.png) [@STierney](https://community.hubspot.com/u/STierney)\
**Post date:** [October 22, 2025, 12:10am UTC](https://community.hubspot.com/t/better-description-for-a-developer-seat/141400/2 "2025-10-22T00:10:20Z")

</div>

Hey @clvtross - thanks so much for posting in the Community!  
I’d first like to point out our [documentation on managing developer seats](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/developer-seats). I believe this will help support a better scope of understanding for your IT team.  
I’d also like to tag in some developer experts just to see if they have any insight that’s worth adding here. @ChrisMagtoto, @PBaxter, and @alyssamwilie - any follow-up thoughts beyond the documentation above?  
Shane, Senior Community Moderator

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [October 22, 2025, 4:07am UTC](https://community.hubspot.com/t/better-description-for-a-developer-seat/141400/3 "2025-10-22T04:07:00Z")

</div>

Hi @clvtross,

Developer seats are for technical configuration, API usage, integrations, and extensibility of the HubSpot platform. This is different from core seats which are for operational users who use the CRM, marketing, and sales tools day-to-day.

You can find the detailed description here: [https://developers.hubspot.com/docs/apps/developer-platform/build-apps/developer-seats](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/developer-seats)

Here is also an overview created with the help of generative AI:

> * * *
> 
> #### 
> 
> **Platform Development & APIs**
> 
> - Access and manage developer tools such as:
> 
> - Use API keys, OAuth apps, and webhooks for integrations
> 
> - Build and test using developer test accounts
> 
> - Work within serverless functions and CMS Hub local development environments
> 
> - Access the HubSpot Developer Projects (projects.json) framework for bundling custom apps, modules, and themes
> 
> #### 
> 
> **Customization & Automation**
> 
> - Create and deploy:
> 
> - Configure HubSpot CRM extensions (CRM cards, timeline events)
> 
> - Access Operations Hub programmable automation with advanced scripting
> 
> - Build and maintain custom UI extensions using React or HubSpot UI components
> 
> #### 
> 
> **Technical Utilities**
> 
> - Access full Breeze AI Developer integrations, including:
> 
> - Test and debug in sandboxed environments
> 
> * * *

Best regards

---

<div class="post-metadata">

**Author:** ![OJ\_ONT](https://avatars.discourse-cdn.com/v4/letter/o/a587f6/32.png) [@OJ\_ONT](https://community.hubspot.com/u/OJ_ONT)\
**Post date:** [November 12, 2025, 4:55pm UTC](https://community.hubspot.com/t/better-description-for-a-developer-seat/141400/4 "2025-11-12T16:55:30Z")

</div>

My bug-bear is why I can’t assign a view-only seat (or view permissions) to a developer. If they are debugging an issue or working on integration, they may need to see data in the CRM? Yes they might be able to use the API to query certain end-points, but it will not be easy to see key settings on forms, web pages etc that might have an impact on the delivery of their work.