You see the scopes before you connect
The Connections screen says exactly what IL Co reads from and writes to Slack, Linear and GitHub — before anyone clicks Connect.
IL Co reads from the tools your team already uses and writes back only what its author approved. These are the controls that exist today — described at the scope they are actually built.
The Connections screen says exactly what IL Co reads from and writes to Slack, Linear and GitHub — before anyone clicks Connect.
The IL Co GitHub App reads pull requests, reviews and commits in repositories you grant. It never commits, opens or merges a pull request, or changes a repository.
A handoff reaches Slack or Linear only after its author approves it. Rejecting it means it is never published.
While a handoff waits for review, only the person it was drafted for can see it.
Connection tokens are held by the IL Co server and encrypted at rest. Each connect handshake is bound to the browser that started it.
Slack commands and Linear webhooks are verified against the provider’s signature, with a short replay window, before anything is queued.
Every request is checked against workspace membership and role. Guests can view, comment and search; they cannot create or change work.
Drafted, edited, approved, published, questioned, reassigned, accepted — every step is recorded on the handoff itself.
A trust page that overstates is worse than one that says less. So, plainly:
IL Co is in private beta with a small number of engineering teams.