Admin
Installing for your workspace
What the Slack install grants, who can do it, and what Gini can reach the moment it lands.
If you're the person who has to sign off on this, here's what the install actually grants and what it doesn't.
What installing does
Adds the Gini app to your Slack workspace and creates a #gini channel. That's it.
Installing does not give Gini access to your channels. Access comes one channel at a time, when someone runs /invite @Gini in it. There's no workspace-wide read, no crawl, and no bulk-import step at any point.
This is the property worth checking against other tools you're evaluating. "Connect your Slack" usually means "index your Slack."
Who can install
Anyone who can add an app to your workspace. If your workspace requires admin approval for apps, Slack routes it to an admin and the install waits: the standard Slack flow, nothing Gini-specific.
What Gini can reach on day one
| Channels it's been invited to | Yes, including history from before it joined |
| Channels it hasn't been invited to | No |
| Private channels it's been invited to | Yes, same behaviour |
| Private channels it hasn't | No |
| DMs between your people | No |
| Files in channels it's in | Yes |
| Your connected tools | Only per person, only what each person connected |
Reviewing before you roll out
A reasonable path for a security-conscious team:
Install and leave it in #gini. It can't see anything else. Try it there.
Invite it to one working channel. Watch how it behaves for a week with real work.
Read what it wrote. app.ginicomputer.com → Wiki shows you exactly what it took from that channel.
Then widen it.
If you need the security packet (trust model, sub-processors, retention, SOC 2 status), it's at ginicomputer.com/security, or email security@ginicomputer.com.
What people can do once it's in
Everyone in a channel Gini has joined can give it work, and they all draw on the same credit balance. There are no per-person seats to assign and adding people doesn't change the bill. See Plans.
What each person can get Gini to do is bounded by their own connections: Gini acts with their access to a tool, never a shared admin account. See How connections work.
Approval policy isn't configurable
There's no admin toggle and no per-tool exemption: approval policy is not a customer-facing setting in either direction. If you're reviewing this for a security sign-off, read Approvals rather than this note: it's specific about which stops are unconditional and where the harder boundary is.
SSO, SCIM and audit export
On Enterprise. Along with volume credit pricing, a DPA, and custom retention windows. Talk to us.
Removing it
One click, and it's genuinely one click. See Removing Gini.