Skip to main content
Shared bots belong to the organisation, while teams provide focused ownership and permissions around the work.

​
Collaboration loop

  1. Create or open a shared bot from the organisation’s Shared bots section.
  2. Add a change with a clear commit message and the current parent version.
  3. Stage the change so teammates can review it without changing production.
  4. Compare and test the change in the bot Changes page.
  5. Commit the reviewed version and promote it through the deployment environments.
Bothive checks the parent version when committing. If somebody else has committed first, refresh the diff and resolve the stale version before retrying.

​
Good defaults for hackathons

  • Give every project team its own team inside the organisation.
  • Keep production deployment approval enabled until the demo path is tested.
  • Use preview deployments for rapid iteration.
  • Store secrets in integrations and never commit credentials into HiveLang.
  • Keep the audit trail enabled so the team can explain what changed before a demo.

​
Enterprise handoff

Before launch, review members and permissions, confirm the production readiness report, test approval-required actions, and verify the rollback target. The same workflow scales from a weekend prototype to a controlled production agent.