Startups without IT
You're 10–100 people, no dedicated admin, and access requests land in someone's DMs.
Cookie Jar
How Cookie Jar works
Install, assign owners, then let your team request access in Slack. Five minutes of setup; one click per request from then on.
who it's for
Built for the messy middle — 10 to 100 people on Slack.
Engineering-led teams
Your founders or eng leads approve tool access today. Cookie Jar gives them a one-click path instead of a Notion doc.
SaaS sprawl
You've got 30+ tools across the workspace and nobody can answer who has Figma.
Building an audit trail
Auditors and procurement teams want an access log. Cookie Jar gives you a queryable record per tool, per person, per date — helpful evidence on the path to SOC 2 even though we don't carry the cert ourselves yet.
Works with any SaaS tool out of the box. Request any with /cookie.
Cookie Jar manages access to SaaS apps directly in Slack. The audit trail is in the dashboard.
- GitHub
- AWS
- Figma
- Google Workspace
- Notion
- Linear
- Jira
- Vercel
- Stripe
- 1Password
- Sentry
- PagerDuty
+ 12 more, or add your own.
The full picture
See it in 60 seconds.
A one-minute walkthrough: install, assign owners, request, approve. No narrator, no fluff.
five-minute setup
Install,
assign, done.
No IT ticket. No procurement call. One Slack admin clicks Add to Slack — three steps later, your team is requesting cookies.
STEP 01
Click Add to Slack
Workspace admin or owner installs Cookie Jar in one click. 24 common tools are pre-loaded — GitHub, Figma, Jira, Notion, AWS, and 19 more.
STEP 02
Assign owners to tools
Open the Shelf in the dashboard. Add one or more owners per tool — head of design owns Figma, head of eng owns GitHub. Two minutes saves a hundred DMs.
STEP 03
Your team grabs cookies
Anyone types /cookie [tool] in Slack. Owners get a DM with Approve / Deny buttons. One click resolves the request. Audit log captures it.
what it actually does
How a request flows,
start to finish.
Automated today Manual today On the Pro roadmap
01
Employee
AUTOMATED
An employee asks for access in Slack
They type /cookie request github (or /cookie like @sarah for a batch). Cookie Jar parses the command and confirms the tool exists on the shelf.
02
Cookie Jar
AUTOMATED
Cookie Jar pings the right owner
It looks up the owner(s) for that tool and DMs them with [Approve] [Deny] buttons. Falls back to admins if no owner is assigned.
03
Owner
AUTOMATED
The owner clicks Approve in their DM
One click resolves the request. Multi-owner committees fan out — whoever clicks first wins, the others' DMs auto-update so nobody double-approves.
04
Owner
MANUAL TODAYAUTO ON PRO ROADMAP
The owner adds the seat in the actual tool
A 30-second manual step in GitHub, Figma, or wherever. The owner is already in the headspace — they just decided yes.
05
Cookie Jar
AUTOMATED
Cookie Jar logs it and notifies the requester
The audit log captures actor, target, tool, and timestamp. The requester gets the outcome in Slack. The dashboard updates in real time.
TRUST POSITIONWHY WE DON'T AUTO-PROVISION
We never integrate with Jira, Figma, Bitbucket, or your other SaaS apps. No stored credentials, no AI touching your accounts. Humans approve. Humans grant. We just keep the record.
Offboarding works the same way, in reverse.
When someone leaves, the admin runs /cookie revoke @user all — Cookie Jar lists every tool they're on and yanks them in one click. The owner who clicks Approve also clicks Remove in the actual SaaS app. Cookie Jar tracks who should be removed; humans do the removing. The leave flow (per-tool checklist + 24h nags + final "Remove forever" gate) ships on Pro.
the admin view
See who has what,
when you want.
Person cards. Tool badges. Filter, search, audit. The dashboard is for monthly review — not daily ops. Your team lives in Slack; you check in here when you want the full picture.
- ✓One row per person, badges for every tool they hold
- ✓Click any tool to see grant history, owner, and audit trail
- ✓Export to CSV for compliance reviews
