Channels and access

Instub's channel model is designed to keep its access minimal and explicit. It can only see channels it has been invited to, and removing it from a channel immediately ends its access.

Invited channels only

Instub does not have workspace-wide read access. It reads a channel only after a human invites it in with /invite @Instub. This is enforced at the Slack permission level, not just by configuration.

Who can tag Instub

By default, any workspace member can tag Instub in a channel it is a member of. Workspace admins can restrict this to specific roles or users in workspace settings under Access control.

Connected integrations and scope

When a team member connects an integration — Notion, Linear, GitHub, etc. — that connection is scoped to them. Instub acts with their permissions, not a shared service account. If they disconnect the integration, jobs that require it will ask before proceeding.

Removing Instub from a channel

To remove Instub from a channel, use /kick @Instub in that channel. Its access ends with the membership. It will not retain memory of the channel after removal.

Uninstalling

To uninstall Instub entirely, go to your Slack workspace settings → Manage apps → Instub → Remove app. All stored context and integration credentials are deleted within 30 days of uninstall.