Hivel Off-boarding Guide

This guide helps your team safely disconnect Hivel from your systems, revoke credentials, and complete all steps required for a secure offboarding.

---

1. Summary Checklist

Please complete the following steps to ensure a full disconnection from Hivel:

• Delete webhooks from Jira, GitHub, GitLab, Bitbucket

• Revoke OAuth access for all Hivel apps (or your internal app name used for the integration) in: Google Workspace (GCal), Microsoft Entra ID (Outlook), GitLab, Bitbucket, GitHub.

• Delete PATs, API tokens, and app passwords

• Rotate any shared secrets used for Hivel

• Validate no events or auth flows reach Hivel

• Share confirmation + evidence with your Hivel representative

---

2. Prerequisites

Before beginning, ensure you have:

• Admin access to your SCM and identity systems

• List of repos/projects connected to Hivel

• Names of OAuth apps or service principals used for Hivel

---

3. Remove All Webhooks

Jira

Path: Admin → Settings → System → Advanced → WebHooks

Steps:

1. Locate all webhooks pointing to Hivel endpoints.

2. Delete them.

3. Validate by triggering an issue update.

---

GitHub

Repository-level: Repo → Settings → Webhooks → Delete Hivel webhooks

Organization-level: Org Settings → Webhooks → Remove Hivel entries

Validation: Push a commit.

---

GitLab

Project → Settings → Webhooks → Delete Group → Settings → Webhooks → Delete

---

Bitbucket

Repo Settings → Webhooks → Delete Workspace Settings → Webhooks → Delete

---

4. Revoke OAuth App Access

Google Workspace (Calendar)

Admin Console → Security → API Controls → App access control → Remove or Block Hivel

---

Microsoft Entra ID (Outlook)

Entra ID → Enterprise Applications → Hivel →

• Disable sign-in

• Revoke admin consent

• Remove user assignments

---

GitHub OAuth / GitHub App

Settings → Applications → Authorized OAuth Apps → Revoke Integrations → Installed GitHub Apps → Uninstall (if used)

---

GitLab OAuth

Preferences → Applications → Revoke Group Settings → Applications → Remove

---

Bitbucket OAuth

Personal Settings → OAuth / Connected Apps → Remove Workspace Settings → OAuth Consumers → Remove

---

5. Delete Tokens and App Passwords

Delete all credentials created for Hivel:

• GitHub PATs: Settings → Developer settings → Personal access tokens (Classic/Fine‑grained) → Delete those issued for Hivel.

• GitLab Access Tokens: Preferences → Access Tokens → Revoke/Delete Hivel tokens.

• Bitbucket App Passwords: Personal settings → App passwords → Delete those used by Hivel.

• Atlassian API Tokens: id.atlassian.com → Security → API tokens → Revoke tokens used by Hivel.

• Secrets in CI/CD: Remove from your secret stores (GitHub Actions secrets, GitLab CI/CD variables, Bitbucket workspace variables, Jenkins credentials, Vault, etc.).

---

6. Optional Cleanup

These actions ensure complete security:

• Rotate shared secrets

• Remove Hivel IPs from allowlists (if any were added)

• Disable Hivel service accounts

• Remove deploy keys

---

7. Validation & Sign-Off

You can use the following Checklist to support your offboarding.

Component	Action	Status	Evidence
Jira Webhooks	Removed	☐
GitHub Webhooks	Removed	☐
GitLab Webhooks	Removed	☐
Bitbucket Webhooks	Removed	☐
Google OAuth	Revoked	☐
Microsoft Entra	Revoked	☐
GitHub/GitLab/Bitbucket OAuth	Revoked	☐
PATs / App Passwords	Deleted	☐
Secrets	Rotated	☐

---

8. Final Submission to Hivel

Please send the completed checklist + evidence to:

📧 [email protected]

Hivel will:

• Stop all ingestion jobs

• Apply your chosen data retention/deletion policy

• Send a confirmation once deletion is complete

---

Data Retention

If your agreement includes data deletion, specify whether you want immediate deletion or retention for X days for audit needs. Hivel will confirm completion and share a deletion certificate/logs as applicable.

---

Support

If you'd like help completing any steps, contact your Customer Success Manager or [email protected].