TL; DR I have App Object, created a permission set → View(all record). Assigned it to the user. That App object’s record not showing. confirming the issue with app object.
I have tested it by giving view all permission on the contact object. That user can able to view the all the contacts not the app object. Same Permission set, i will share the SS below (hiding app object and permission set’s name). User Permission for that user updating(contact not the app object) when change the permission set.
One thing I’d check is whether the issue is actually the permission set or the app object’s visibility configuration.
Since giving View All on Contacts works, it sounds like the permission set is being applied correctly. That narrows the problem to the app object itself rather than user permissions in general.
A few things I’d verify:
Is the app object enabled for that specific user or team?
Does the app object have its own object-level permissions that need to be granted in addition to the permission set?
Is the user assigned the correct app access/license if this object comes from a private app or marketplace app?
If you’re testing with an existing record, is there any record-level ownership or filtering preventing it from appearing?
If you can share:
whether this is a custom object or an app-created object,
how the object was created (private app, public app, or custom object),
and a screenshot of the permission configuration,
it’ll be much easier to narrow down where the access is breaking
I would separate record access from UI visibility before changing the permission set again. First, have the affected user open one known record by its direct URL. Second, test whether the same user can see a record created after the permission assignment, not only older records. Third, compare the app object’s internal object type ID in the permission set with the ID used by the record page. If direct access works but the list stays empty, the issue is likely in the app object view or card configuration. If direct access also fails, capture the user ID, object type ID, record ID, and the correlation ID from the failing request for HubSpot support. I’m Ege, co-founder of Atlantic, based in SF; splitting the access test from the presentation layer usually makes these permission bugs easier to pin down.
Since Contacts behave normally but the app object does not, this does look like an app-object-level visibility/config issue rather than a general permission-set problem.
The settings in your screenshot also make me think the object may not be intended to behave like a standard CRM object for sharing.
If you want, I’d check whether the app object creation in the public app project has its own access model or sharing restrictions that override the permission set
tried it @stassey . it is great to create the custom object in development but this permission thing. i don’t know what to say. is it a bug or restriction ? what is the cause of this behavior ?
really tired of hubspot developer experience. it would be help if this resolved. i thought i had break through in the integration development. nah just walls and hurtles.
PS: I tried published integrations named “Applicant Tracking System ATS”. It features APP object. i created one from super admin and tried to share it all same. is this permission set bug/issue only for app objects ? @stassey@chighsmith
Please note - this post has been edited by a Community moderator to ensure it adheres to our Community Guidelines.
That would be great. if you said is true, Hubspot needs put some explanation or something about this in the app object section. I tried again this time, now it is updating idk what happened (bug or glitch) or hubspot fixed it. currently it works .
Glad it is working now! Yes, it definitely seems like there was an error in HubSpot or something. I hope it will remain fixed. Thank you for the information!
Thanks for the followup. As you’ve stated the original issue was resolved, does this new record/ scenario follow all of the same parameters as before?
From my understanding the previous issue was not resolved internally as there was no record of a change from our end. That said, it looks like this would’ve been resolved on your end. You’ve stated this issue persists with a new/ different record. Is that correct?
From your most recent screenshot are you stating that there are no available Users or Teams to choose from? Could you please share the respective permissions of the User or Team that you’re hoping to share with?
I will keep you updated on next steps.
. Really Appreciate that.