topic Re: "Edit Property Settings" required despite basic OAuth scopes in APIs & Integrations

"Edit Property Settings" required despite basic OAuth scopes

Leadjet — Tue, 11 May 2021 10:00:05 GMT

Hi all!

Our App currently has 4 OAuth scopes enabled: "contacts", "crm.import", "oauth" and "sales-email-read".

However, our customers are forced to grant the "Edit property settings" to their employees in their User & Team settings so that these employees can use our App. For some admin, turning on this option is too much privileges given to their teammates...

So my question is what can we do not to have to turn this option on, since our App won't need this a priori to work properly (we do not create or delete properties).

Thank you!

Re: "Edit Property Settings" required despite basic OAuth scopes

dennisedson — Tue, 11 May 2021 17:35:33 GMT

Hi @Leadjet

Is this something that a superadmin can install for all?

@himanshurauthan , how would you handle this?

Re: "Edit Property Settings" required despite basic OAuth scopes

himanshurauthan — Wed, 12 May 2021 08:33:25 GMT

Thank you @dennisedson for counting me in. 😀

So @Leadjet coming to your query now.

Can you please explain a bit what your app is doing, and is this issue while installing the app or using the app? If it's for the installation I would recommend letting the super admin install the app, as the installation is a one-time process.

Regards,

Re: "Edit Property Settings" required despite basic OAuth scopes

Leadjet — Wed, 12 May 2021 08:59:42 GMT

Thanks @dennisedson and @himanshurauthan

Leadjet allows salespeople to manage and add contacts right from LinkedIn. https://leadjet.io/

We require every salesperson's to connect via OAuth to their Hubspot instance for us to access their token and perform requests on their behalf. This steps allows us to create a User account for every new comer.

While attempting to connnect to Hubspot via OAuth, some users face the following message:

The workaround we found was to ask the admin to enable, for every sales who wants to use Leadjet, the "App Marketplace Access" and "Edit Property Settings" from the Users settings.

The issue is that while admins do not worry about granting the "App Marketplace Access" option to their users, some are more careful with the "Edit Property Settings", which causes frictions. Since we don't understand why we need this particular option to be enabled in the first place, I'm seeking help on how to get rid of this requirement.

Let me know if it's clear 🙂

Re: "Edit Property Settings" required despite basic OAuth scopes

dennisedson — Thu, 13 May 2021 14:08:42 GMT

@Leadjet

I believe this comes down to a limitation in the granularity that we offer for scopes. I know that this is currently being addressed. Unclear on an exact timeline, but would anticipate something by Q3.

In the interim, I believe the admin can grant them that access and after installation, can remove that access. I know it is a hack, but I think that is the best bet for now.

Re: "Edit Property Settings" required despite basic OAuth scopes

Leadjet — Fri, 14 May 2021 10:11:08 GMT

Thanks for the info @dennisedson !

In the meantime, as you suggest, I'll ask our customers to grant this rights just during the installation, that should do it.

Thanks!

Re: "Edit Property Settings" required despite basic OAuth scopes

Leadjet — Tue, 02 Nov 2021 15:47:45 GMT

Hello @dennisedson ,

Circling back on this: I saw the new update regarding scope granularity is coming out soon.

Do you know, by any chance, if it will solve this issue?

Right now, this causes quite a lot of friction in our onboarding for some users. Sometimes upgrading all users of a potentiel client company to super-admin privileges is even needed, despite the fact we have basic OAuth scopes.

Any help on this would be really appreciated 🙂

Thanks!

Re: "Edit Property Settings" required despite basic OAuth scopes

dennisedson — Mon, 08 Nov 2021 18:36:28 GMT

I am hoping so!

Re: "Edit Property Settings" required despite basic OAuth scopes

Bozwot — Mon, 17 Jul 2023 18:10:30 GMT

Hello all- checking if this issue has been resolved since the updates a few years ago. Thanks