# OAuth

OAuth registers applications and issues tokens for authorized access to Socra services. Client registrations belong to a Project, while issued tokens are scoped to an Account.

## Why use OAuth?

An application needs an identifiable client and an authorized way to call services. OAuth provides that registration and consent path, with configuration for the application that users authorize.

## What you can do

- Configure the application's name, branding, audience, and authorized domains.
- Register web, browser, or native clients with their redirect settings.
- Create and remove client secrets for clients that use them.
- Manage Account-owner consent through Installations and exchange client credentials for an installation token.

## Core concepts

An **OAuth config** holds Project-level application settings. A **Client** is a registration for a particular application runtime. An **Installation** records an Account owner's consent for a Project's requested scopes.

Requested scopes must correspond to services enabled for the client Project. OAuth establishes authorized token access; IAM policies govern operations on Project resources. Client secrets are credentials, so retain them securely when created.

## Use OAuth

Read the [CLI reference](/docs/oauth/reference/cli) for commands or the [API reference](/docs/oauth/reference/api) for resources, request fields, and responses.

## Related services

- [Projects](/docs/project)
- [IAM](/docs/iam)

---

Company: Socra — Multiply Your Judgment
Canonical URL: https://cloud.socra.com/docs/oauth