Organization handbook

Docs for public API teams.

Use this page to keep member access, repository standards, launch readiness, and security expectations easy to follow.

Current mode Public collaboration

Repos stay open, docs stay readable, and maintainers keep decisions visible.

01

Member Access

Invite contributors by exact GitHub username. Start with member access, then promote only trusted maintainers who need organization settings.

02

Repository Standards

Each repo should include setup steps, API route docs, environment variable names, deployment notes, a license, and a security contact path.

03

API Launch Checklist

Before publishing, confirm the landing README, examples, health route, error format, and deployment workflow are accurate.

04

Review Flow

Keep pull requests focused. Ask for review when behavior changes, tests are added, or public API responses are updated.

05

Security

Never commit secrets. Use repository secrets for deploy tokens, rotate leaked keys immediately, and document required credentials by name only.

06

SAML Readiness

Enable SAML only after identity-provider details are tested. Keep SAML enforcement off until every active member has authenticated.