OAuth Consent for Marketplace Apps in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Sparkforge’s OAuth consent screen lists every permission a Marketplace app is requesting before you install it, with explicit warnings on sensitive scopes like creating users.

Sparkforge’s OAuth install flow now shows a clear permission summary before you authorize a Marketplace app. You see the app, the scopes it wants, and explicit warnings when an app asks for sensitive access.

What changed

OAuth lets third-party apps request access to specific parts of your Sparkforge account — contacts, calendars, conversations, workflows, and more. Previously, clicking an OAuth link sent users straight into authorization without a permission preview. Now the flow surfaces:

The app name and logo.
The full list of requested OAuth scopes.
A plain-language explanation of what each scope allows.
Warnings on sensitive permissions like users:write.

The same screen appears for both standard Marketplace links and grey-labeled installs.

How the consent flow works

When a user clicks an OAuth install link from an app’s integration page, Sparkforge sends them to a confirmation screen with the app branding, the full scope list, scope-by-scope explanations, and a warning panel for any high-risk access.

Example link format:

https://marketplace.sparkforge.com/oauth/chooselocation?...

Grey-labeled experience

White-labeled installs use the same consent flow on URLs like:

https://marketplace.sparkforgehq.com/oauth/chooselocation

Permission visibility and warnings are identical regardless of which domain hosts the install.

Reading scopes and warnings

Scopes describe exactly what an app can do. Common examples:

contacts:readonly — view your contact list.
conversations:write — send messages on your behalf.
locations:readonly — view account location details.
users:write — modify team members or create new users (flagged with a warning).

Best practices for authorizing apps

Read the scope list before approving — do not authorize blindly.
Only install apps from developers you trust.
Skip apps that request more access than the feature needs.
Audit installed apps regularly under Settings > Connected Apps.
Revoke access for apps you no longer use.

Frequently Asked Questions

What happens if I deny access at the OAuth screen?

The app is not installed and no data is shared. Authorization is required before any access is granted.

What are scopes in OAuth?

Scopes define exactly which data and actions a third-party app can touch. They limit what an integration can do in your account.

How do I know if a scope is sensitive?

Sensitive scopes like users:write or locations:write trigger a bold warning panel on the consent screen.

Does this apply to apps I have already installed?

No. The new consent flow only runs on new installs and re-authorizations. Existing installs are not changed retroactively.

Does OAuth consent work for private apps?

Yes. Private apps using OAuth route through the same screen and show the same scope details and warnings.