Team & lifecycle

Hover Cloud is multi-tenant: an org (team) owns projects, each project is one GitHub repo, and every project holds its ingested runs. This page covers inviting teammates, alert channels, scheduled monitoring, and the lifecycle operations — rotating tokens, deleting things.

Invite teammates

Under Settings, an owner or admin can invite a teammate by email with a role of member or admin. The invite is emailed as a link; the teammate signs in with GitHub and lands in the team with the role you chose. Pending invites show on the team card and can be revoked before they're accepted.

Roles: owner and admin can change CI configuration, manage environments and accounts, and run the destructive operations below; member has read access to runs and dashboards.

Alert channels

• Email — regression alerts go to the project's team automatically.
• Slack — paste an incoming-webhook URL under Settings → Slack alerts and regressions post there too. Leave it empty and save to turn it off.

Scheduled monitoring

Under Configure → CI settings, set a monitor cron (five fields, e.g. 0 * * * * for hourly) and the environment to monitor. Cloud adds a schedule trigger to your workflow so your CI runs the suite on that cadence — the compute stays on your side. A failure on a monitored run raises a regression alert like any other.

Rotate the ingest token

If the per-project ingest token leaks, rotate it from Configure → Danger zone → Rotate ingest token. Cloud mints a new token, updates the repo's HOVER_INGEST_TOKEN secret in place, and stores the new hash. The old token stops working immediately. The new plaintext is shown once, in case you wired it anywhere by hand.

Deleting things

All under Configure → Danger zone (owner/admin only):

• Remove a test account — deletes its GitHub secrets and drops the name from the workflow (once no other environment uses that label).
• Delete an environment — removes the GitHub Environment, its scoped secrets, and its workflow entry. Past runs stay.
• Delete a project — removes the project and all its ingested runs from Cloud. Your repo keeps its workflow and secrets; delete those in GitHub yourself if you want them gone.

Team-level operations are under Settings → Leave or delete team:

• Leave a team — you leave; the team and its projects stay. A sole owner must hand ownership over first.
• Delete a team (owner only, name-confirmed) — removes the team and every project and run under it. Repos keep their workflows and secrets.