Channels & access
engineer9 starts with access to nothing. You decide which channels it can see, one at a time. This is the foundation of keeping sensitive conversations out of its reach.
Default-deny
Section titled “Default-deny”When engineer9 joins your workspace, it cannot read any channel. You add the channels it should listen to, typically project or team channels, from the Channels page in your dashboard. Only added channels are ever read; everything else stays invisible.
Adding and removing channels
Section titled “Adding and removing channels”On the Channels page:
- Add a channel to grant engineer9 access to it. Search your workspace’s channels and add the ones it should be active in.
- Remove a channel to revoke access. Removing it stops engineer9 from reading new activity there.
When you add a channel later, engineer9 begins learning it from that point forward. It reads new activity going forward and does not retroactively scan the channel’s history.
Give it a few days
Section titled “Give it a few days”Right after you add channels, engineer9 knows almost nothing, and that’s expected. It builds its Memory and Roster by listening over the following days. Within a couple of days it starts to know who owns what and can answer with real context. If it says it doesn’t know something early on, that’s the honest answer.
The roster it builds
Section titled “The roster it builds”From activity in your added channels, engineer9 builds a roster of who owns which area. You can review it on the Team page in your dashboard. To correct an entry that’s wrong, tell engineer9 in Slack and it updates the roster as it learns.