CoreView (FKA 4ward365) OAuth Scopes

OAuth 2.0 searched

CoreView (FKA 4ward365) publishes 14 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the CoreView (FKA 4ward365) API on a user’s behalf.

Tokens are issued from https://identity.coreview.com/connect/token.

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.

CompanyMicrosoft 365SaaS ManagementGovernanceSecurityIdentityAutomationWorkflowLicense ManagementIT Operations

Scopes: 14 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://identity.coreview.com/connect/token

Flows
clientCredentials

Scopes (14)

Scope	Description	Flows
customer.read	Read access to customer/tenant configuration.	clientCredentials
customer.write	Manage customer/tenant configuration.	clientCredentials
delegation.read	Read delegated administration assignments and roles.	clientCredentials
delegation.write	Manage delegated administration assignments and roles.	clientCredentials
operator.read	Read operator (administrator) accounts and their permissions.	clientCredentials
operator.write	Manage operator (administrator) accounts and their permissions.	clientCredentials
platform.read	Read platform-level reporting and governance data.	clientCredentials
licensepool.read	Read Microsoft 365 license pool allocations.	clientCredentials
licensepool.write	Manage Microsoft 365 license pool allocations.	clientCredentials
license.read	Read Microsoft 365 license assignments and inventory.	clientCredentials
openid	Standard OpenID Connect scope requesting an ID token.	clientCredentials
profile	Standard OpenID Connect profile claims.	clientCredentials
email	Standard OpenID Connect email claim.	clientCredentials
offline_access	Request a refresh token for long-lived access.	clientCredentials

📄 Provider scope reference: https://help.coreview.com/api-authentication

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: https://identity.coreview.com/.well-known/openid-configuration
docs: https://help.coreview.com/api-authentication
schemes:
- name: OAuth2ClientCredentials
  source: https://help.coreview.com/api-authentication
  flows:
  - flow: clientCredentials
    tokenUrl: https://identity.coreview.com/connect/token
scopes:
- scope: customer.read
  description: Read access to customer/tenant configuration.
  flows: [clientCredentials]
- scope: customer.write
  description: Manage customer/tenant configuration.
  flows: [clientCredentials]
- scope: delegation.read
  description: Read delegated administration assignments and roles.
  flows: [clientCredentials]
- scope: delegation.write
  description: Manage delegated administration assignments and roles.
  flows: [clientCredentials]
- scope: operator.read
  description: Read operator (administrator) accounts and their permissions.
  flows: [clientCredentials]
- scope: operator.write
  description: Manage operator (administrator) accounts and their permissions.
  flows: [clientCredentials]
- scope: platform.read
  description: Read platform-level reporting and governance data.
  flows: [clientCredentials]
- scope: licensepool.read
  description: Read Microsoft 365 license pool allocations.
  flows: [clientCredentials]
- scope: licensepool.write
  description: Manage Microsoft 365 license pool allocations.
  flows: [clientCredentials]
- scope: license.read
  description: Read Microsoft 365 license assignments and inventory.
  flows: [clientCredentials]
- scope: openid
  description: Standard OpenID Connect scope requesting an ID token.
  flows: [clientCredentials]
- scope: profile
  description: Standard OpenID Connect profile claims.
  flows: [clientCredentials]
- scope: email
  description: Standard OpenID Connect email claim.
  flows: [clientCredentials]
- scope: offline_access
  description: Request a refresh token for long-lived access.
  flows: [clientCredentials]
notes: >-
  Scope names are taken verbatim from the CoreView OIDC discovery document
  (scopes_supported) and the API authentication documentation. Descriptions are
  derived from the scope naming (resource.read / resource.write) and CoreView's
  documented delegation, operator, platform, and license-management domains.