People and permissions

There are no seats to assign and no roles to configure. Everyone draws on the same workspace credit balance.

What differs between two people isn't a permission we hold for them. It's what each of them has connected.

Why there are no seats

Per-seat pricing would mean deciding in advance who's allowed to ask, and buying a seat for someone who uses Gini twice a month. You pay for work Gini does instead. Adding your whole team changes nothing on the bill.

The practical effect: you don't have to gatekeep. Let people use it.

What bounds what someone can do

Their channels. Gini works with the context of the channel you're in. Someone who isn't in #finance doesn't get #finance answers by asking Gini.

Their connections. Gini acts with your access to a tool. Two people asking the same question can correctly get different answers, and nobody gains access by routing through Gini. See How connections work.

The approval gate. Anything irreversible stops for a person, whoever asked. Nobody has a level of trust that skips it.

Onboarding someone

Nothing to provision. They join the channels, they can ask.

Two things worth telling them:

• Connect your own tools at app.ginicomputer.com → Integrations. Without that, Gini can only work from the channel.
• Ask the wiki before asking a person. It's the fastest onboarding tool you have, and the questions people are shy about asking twice are exactly what it's good at.

Offboarding someone

This is the one that needs a checklist, because their connections leave with them.

1. Reassign their routines. app.ginicomputer.com → Routines, filtered by owner. A routine running on their Google access stops when the access goes.
2. Have someone else connect the tools those routines need.
3. Deactivate them in Slack as normal. Their access to Gini ends with their Slack account.
4. Check the wiki. What they knew stays, which is the point. What they connected doesn't.

Skip step 1 and you'll find out when a routine fails and says so in its channel. Not a disaster: just avoidable.

Restricting who can use it

Slack membership is the lever. Someone who isn't in a channel Gini is in can't direct it there.

If you want a tighter boundary than that, the answer is usually fewer channels rather than more configuration.

SSO and SCIM

Enterprise, along with audit log export, a DPA, custom retention, and volume credit pricing. Talk to us.

Watching what it's being used for

app.ginicomputer.com → Usage shows credit spend and what it went on.

Read it monthly and you'll see two things: which team is getting the most out of it, and which routine is quietly the most expensive thing you run.