Admin
Channels and access
Gini reads a channel only after someone invites it. How to widen that, narrow it, and audit it.
Channel membership is the permission model. There's no separate access control panel, because there doesn't need to be one: Gini can read exactly the channels it's a member of, and Slack already shows you that.
Adding a channel
In the channel: /invite @Gini.
When it joins it reads the channel's history, then posts one introduction saying what it understands the channel to be about and offering two or three specific jobs it could take on. On a long history that takes a few minutes.
Reading history on join is what makes it useful immediately rather than in three weeks. It's also the moment to think about whether this channel should have Gini in it at all.
Removing a channel
/remove @Gini in the channel, or remove it from Slack's member list.
Access ends with the membership. It can't read new messages and it can't re-read the history.
Removal is not retroactive
What Gini already learnt from that channel (its wiki pages, facts and skills) stays until you delete it. Removing Gini from a channel because something sensitive was said there is the second step. The first is deleting what it kept.
Which channels to put it in
Good: project channels, team channels, ops channels, anywhere decisions get made and work gets coordinated. The value scales with how much real work happens in the room.
Think first: anything client-facing or shared with an external organisation. Gini behaves the same way, but the room is bigger than your company.
Probably not: compensation, legal, anything under NDA, and #general. The first three because you don't want it written down. #general because it's noise, and noise makes the wiki worse.
Auditing what it can see
Slack shows this natively: Gini's profile → the channels it's in. That list is complete and it's the whole answer.
Cross-check it against what Gini has written down at app.ginicomputer.com → Wiki. Every page traces back to a channel.
Private channels
Same rules, no exceptions. Gini can be invited to a private channel and behaves identically there. It cannot see a private channel it hasn't been invited to, and no admin setting changes that.
Inviting Gini to a private channel doesn't make its contents visible to people outside that channel. But it may produce wiki pages that everyone can read. See How pages get written for keeping a channel out of the wiki.
DMs
Anyone can DM Gini. That's a private conversation between that person and Gini, and it uses their own connections.
Gini can't read DMs between other people, and there's no admin view of what someone asked it in a DM.
Channel limits
Free covers 10 channels. Team and Enterprise are unlimited. Plans.
Turning it off everywhere at once
Remove the app from the workspace. See Removing Gini. Access to every channel ends at the same moment.