Access is a tool for a named piece of work. It is not membership, status, or a permanent reward for having helped before.
The ordinary accounts
| Account | Use | Baseline rule |
|---|---|---|
| Discord | Team conversation and coordination. | Use your own account; do not send secrets or confidential reports. |
| Wildbase Work | Tasks, proposals, work status, and durable decisions. | Put work here before opening a code change. |
GitHub wildbasehq organisation | Source, pull requests, checks, and review. | Multi-factor authentication is required. |
| Development Clerk application | Local Packbase sign-in. | Use a development tenant and its publishable key; never substitute production. |
| Local PostgreSQL and object storage | Server and data work. | Use isolated data you are allowed to destroy. |
| Production providers | Deployments, runtime settings, logs, data, and storage. | Access is never implied by repository access; it must be granted for a named operational task. |
Use separate personal accounts rather than a shared or family login. Store credentials in a password manager. Do not copy a credential into the task that requests it.
Get the first account
The durable-task rule cannot apply before you can reach the task system. If you were invited through Discord but cannot yet use Wildbase Work, reply to the person who invited you or in the shared onboarding thread. If that route is unavailable, use the contact page to send a non-sensitive onboarding request.
Include only your name or handle, who invited you when known, and the area you intend to help with. Do not send a password, token, identity document, private customer material, or production detail.
The person handling onboarding must identify the current Wildbase Work access granter and, for code work, the relevant repository maintainer or reviewer. Once Wildbase Work access exists, create or update the onboarding task and put later access requests there. Wild HQ does not currently maintain a complete public owner directory, so do not infer authority from old commits or who happens to be online.
Ask for a capability, not “full access”
After bootstrap, an access request belongs on the durable task and says:
- the repository, service, or environment;
- the exact action the volunteer needs to perform;
- why local or read-only access is insufficient;
- how long the need is expected to last; and
- who can remove or narrow the permission afterwards.
The request contains no password, token, private key, customer record, or vulnerability detail.
Repository read, pull-request review, merge, deployment, runtime configuration, production logs, production data, billing, and moderation are different permissions. Granting one does not grant the others.
Current secret-transfer limit
Wild HQ does not have a secure submission or shared-secret transfer channel. Discord, GitHub, Wildbase Work, ordinary email, and online AI tools are not substitutes.
Prefer one of these outcomes:
- create your own development credential;
- change the task so it can be completed with public, mocked, or disposable local data;
- have an already-authorised operator perform the protected step and record the non-sensitive result; or
- mark the task blocked until a safe access method exists.
Never solve the gap by sending a production secret through an unsafe route. A reply saying “go ahead” does not make the route secure.
Production and personal data
Production access must be read-only unless the task names a required write. Before querying data, state the question and the minimum fields needed. Do not export a broad table to answer a narrow question. Redact logs before attaching them to a task or pull request.
For a destructive or user-visible action, record the target, expected effect, recovery path, and verifier before acting. If the target cannot be identified exactly, stop.
Review and return access
Review access when a task finishes, a role changes, or a volunteer pauses. Remove permissions that no longer have a current purpose. Rotate a credential if it was exposed, shared with the wrong person, stored in the wrong place, or retained by an account that should no longer have it.
Removing access is ordinary housekeeping. It is not a judgement about the volunteer.