Request and approve access in Slack.
Access requests belong where your team already is. People ask with /driply, approvers decide in one click, and every decision is captured, with full parity on the web.
Wesley Crusher used /driply
“New cadet onboarding”
Driply puts the access approval workflow inside Slack, where your team already works. Someone types /driply, picks a tool, the access levels and the seat, and adds a reason; the approver gets a single message with everything they need, who’s asking, the level, peer access, and the seats and cost remaining, and decides in one click.
There’s no separate portal to adopt, and everything mirrors to the web for admins who want the full picture.
Adoption, for free
A control only works if people use it. Because requests live in Slack, the right way to ask for access is also the easiest, so the record stays accurate instead of going stale the day after onboarding.
Decisions with context
Approvers don’t leave Slack to dig for context. The request card carries the requester, the tool and level, who else holds comparable access, and the seats and cost remaining, enough to say yes or no without a back-and-forth.
Captured as evidence
The moment a decision is made, the grant or denial, its reason, its actor, and an expiry are written to the append-only Event log. Nothing to copy into a spreadsheet, nothing to reconstruct later.
Slack-first, with full web parity
Requests, approvals, and notifications all run natively in Slack, and everything available there has full parity on the web, for admins and anyone who prefers it. Tool owners and admins are notified of the requests that are theirs to decide, so the right person sees it without a manual hand-off.
Driply records the decision; your administrator or the tool’s owner performs the actual change in the target tool. That separation is deliberate. It keeps Driply a clean system of record with no privileged write-access to maintain.
The result, The right way to ask for access becomes the easiest way.
Questions, answered.
- How do access requests work in Slack?
- Someone runs /driply, picks the tool, the access levels and the seat, and adds a reason. The approver gets a single Slack card with full context and approves or denies in one click, and the decision is recorded automatically.
- Do I have to use Slack?
- Slack is where requests and approvals are most frictionless, but everything has full parity on the web, so you can run the entire workflow there too.
- Does approving in Slack grant the access automatically?
- No. Approving records the decision and the grant; your admin or the tool’s owner makes the actual change in the tool. Driply never writes to your tools by design, it’s your system of record and proof, not a switch.