Bright Funds · OAuth Scopes

Bright Funds OAuth Scopes

OAuth 2.0 searched

Bright Funds publishes 7 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Bright Funds API on a user’s behalf.

Tokens are issued from https://www.brightfunds.org/oauth/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.

CompanyWorkplace GivingCorporate Social ResponsibilityEmployee EngagementNonprofitsGrants ManagementDonationsVolunteeringOAuthOpenID Connect

Scopes: 7 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://www.brightfunds.org/oauth/authorize

Token URL
https://www.brightfunds.org/oauth/token

Flows
authorizationCodeclientCredentials

Scopes (7)

Scope	Description	Flows
openid	OpenID Connect authentication; issue an id_token for the subject.	authorizationCode
profile	Access the user's profile claims (name, given_name, family_name, zoneinfo, updated_at).	authorizationCode
email	Access the user's email claim.	authorizationCode
name	Access the user's name claim.	authorizationCode
offline_access	Issue a refresh_token for long-lived access without the user present.	authorizationCode
write	Write access to the Bright Funds platform resources.	authorizationCode, clientCredentials
update	Update access to the Bright Funds platform resources.	authorizationCode, clientCredentials

📄 Provider scope reference: https://www.brightfunds.org/.well-known/openid-configuration

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: https://www.brightfunds.org/.well-known/openid-configuration
docs: https://www.brightfunds.org/.well-known/openid-configuration
schemes:
- name: OAuth2
  source: well-known/bright-funds-openid-configuration.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://www.brightfunds.org/oauth/authorize
    tokenUrl: https://www.brightfunds.org/oauth/token
  - flow: clientCredentials
    tokenUrl: https://www.brightfunds.org/oauth/token
scopes:
- scope: openid
  description: OpenID Connect authentication; issue an id_token for the subject.
  flows: [authorizationCode]
  sources: [well-known/bright-funds-openid-configuration.json]
- scope: profile
  description: Access the user's profile claims (name, given_name, family_name, zoneinfo, updated_at).
  flows: [authorizationCode]
  sources: [well-known/bright-funds-openid-configuration.json]
- scope: email
  description: Access the user's email claim.
  flows: [authorizationCode]
  sources: [well-known/bright-funds-openid-configuration.json]
- scope: name
  description: Access the user's name claim.
  flows: [authorizationCode]
  sources: [well-known/bright-funds-openid-configuration.json]
- scope: offline_access
  description: Issue a refresh_token for long-lived access without the user present.
  flows: [authorizationCode]
  sources: [well-known/bright-funds-openid-configuration.json]
- scope: write
  description: Write access to the Bright Funds platform resources.
  flows: [authorizationCode, clientCredentials]
  sources: [well-known/bright-funds-openid-configuration.json]
- scope: update
  description: Update access to the Bright Funds platform resources.
  flows: [authorizationCode, clientCredentials]
  sources: [well-known/bright-funds-openid-configuration.json]
notes: >-
  Scopes are taken verbatim from the published scopes_supported list in the OIDC discovery
  document. Flow-to-scope mapping is inferred (the discovery doc does not per-scope-map flows);
  standard OIDC scopes bind to the authorization_code flow.