Connecting Malveon takes about fifteen minutes. Before you start, make sure you have the access each connection needs.
Access you need
You need admin access to at least two of the tools you want to connect, because OAuth connections are authorized at the workspace or organization level. Start with two and add more later; the system works with whatever you connect.
- A Slack workspace where you can approve an app
- A GitHub organization where you can authorize OAuth and add webhooks
- A Jira or Linear project you administer
- Optionally, a Datadog, PagerDuty, Sentry, or Vercel account for ops signals
What each connection asks for
Each connection requests scoped, revocable access over OAuth. Malveon’s behavior is read-oriented (it reads metadata: titles, statuses, events), and it writes only when you ask it to. The exact scopes per provider, and how tokens are stored, are documented on the OAuth and access page under Security & Privacy.
You stay in control
Every connection is something you authorize and can revoke from your settings at any time. Revoking invalidates the stored token immediately.