Code or builder access
A repository is ideal for exported or developer-owned projects. Builder projects may use collaborator access, a project copy, read-only sharing, or an export. The first review can often begin with the public URL and error details.
Hosting and deployment
Build failures and production-only bugs may require deployment logs, runtime versions, environment-variable names, routing settings, and later a limited collaborator role. Share variable names, not secret values, during intake.
Data, authentication, and payments
Use a safe test account and non-production or test-mode data wherever possible. Supabase, Firebase, Stripe, and similar systems should be shared through their role-based access tools—not by sending the owner password.
Domains and email
DNS, SSL, and email-delivery repairs may require screenshots or a record inventory first, then temporary role-based access. Existing records should be documented before anything changes.