Interactive
Use browser authorization with PKCE. Never paste provider credentials into commands or agent prompts.
Documentation
This implementation path keeps account setup, provider authorization, evidence ingestion and production permissions separate. Commands are illustrative until the relevant public distribution is released.
sf auth login --environment live sf context set --workspace ws_123 --site site_123 sf sites health
Quickstart
Subscribe and create the workspace
Evidence, owner and next state remain visible.
Add a site without granting production authority
Evidence, owner and next state remain visible.
Authorize analytics and search providers
Evidence, owner and next state remain visible.
Authorize GitHub or WordPress with least privilege
Evidence, owner and next state remain visible.
Run readiness and baseline checks
Evidence, owner and next state remain visible.
Configure budgets, reviewers and schedules before activation
Evidence, owner and next state remain visible.
Authentication
Use browser authorization with PKCE. Never paste provider credentials into commands or agent prompts.
Create a revocable token inside an authorized workspace and restrict it to required operations, site and environment.
Scopes
Rate limits
Published limits can vary by plan and endpoint. Read returned limit, remaining, reset and Retry-After headers; use backoff with jitter and never retry non-idempotent requests blindly.
Errors
{
"error": {
"code": "scope_denied",
"message": "Token cannot access this site",
"request_id": "req_example"
}
}Paid deployment · human authority
Product and developer access require a paid plan.