Quantive · OAuth Scopes

Quantive OAuth Scopes

OAuth 2.0 searched

Quantive uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyBusiness ApplicationsOKRStrategy ExecutionGoal ManagementPerformance ManagementSaaS

Scopes: 0 Flows: Method: searched

Scopes (0)

Quantive implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference: https://www.workboard.com/developer

Source

OAuth Scopes

generated: 2026-07-20
method: searched
source: https://www.workboard.com/developer
api: WorkBoard REST API (Quantive)
docs: https://www.workboard.com/developer
flow: authorization_code
notes: >-
  The WorkBoard REST API v1.0 documents a single coarse OAuth scope. No
  fine-grained scope taxonomy is published, and no OpenAPI declares per-operation
  scopes, so this is the complete documented set.
scopes:
- name: all
  description: >-
    Default scope value granting full access consistent with the authorizing
    user's permissions. Documented as the default value for the scope parameter
    in WorkBoard API v1.0.
  default: true