Agiled Docs

OAuth consent pages appear when an external app or provider asks you to approve access.

Use this page to decide whether an app should connect to your Agiled account or workspace. Consent is a security decision, not just a login step.

Pause when the requested access is broader than the task you expected. A legitimate app should have a clear reason for read, write, or offline access.

Before Approving

Check the app name, requested permissions, workspace, and account you are signed in with. Approve only when you trust the app and understand what access it needs.

If you belong to multiple workspaces, confirm the workspace shown on the consent screen is the one the external app should access. Deny the request if the app, workspace, or requested access does not match what you expected.

If you started from a third-party app, make sure the browser did not switch to a different Agiled account during sign-in. A consent screen can be valid but still belong to the wrong workspace or user.

Scopes You May See

Confirm your account identity for openid.
Read your profile name for profile.
Read your email address for email.
Read workspace records through MCP tools for mcp:read.
Create or update workspace records through MCP tools for mcp:write.
Stay connected until access is revoked for offline_access.

Approve or Deny

Select Allow access to approve the request. Select Deny if you do not recognize the client or do not want to grant the requested access.

Grant write access only when the app needs to create or update records. For read-only reporting, dashboards, or search tools, read access is usually enough.

If you are unsure why an app needs write or offline access, deny the request and ask the app owner to explain the exact workflow before approving.

Scope Review

Before allowing access, ask:

Which workspace will the app access?
Which user is granting access?
Does the app need read access only?
Does it need to create or update records?
Does it need to stay connected when you are offline?
Who will revoke access when the app is no longer used?

Return to the app that started the authorization and try again. If the same error continues, check whether you are signed into the correct Agiled workspace and whether your role allows the requested access.

Also check whether pop-up blockers, stale browser sessions, or an expired authorization attempt interrupted the flow. Start again from the external app so the request parameters are fresh.

If consent repeatedly fails after signing in, try a private browser window with only the intended Agiled account and provider account signed in.

Revoke Access

If an app should no longer connect, remove or disconnect it from the relevant integration or API settings when available. After revoking access, ask the external app admin to remove stored tokens on their side too.

After revoking, test the external app so you know whether the connection was fully removed or whether another admin-level integration is still active.

Confirm The Connected Account

After consent succeeds, return to Agiled and confirm the connected provider account is the one that owns the data or calendar you need. A successful OAuth approval with the wrong Google, Microsoft, HubSpot, or Slack account can look connected while syncing the wrong workspace.

Run one low-risk sync, booking, notification, or import before relying on the connection for customer work.

OAuth Consent