qURL for Slack
Private access, right from Slack.
Your apps, APIs, and files aren’t on the internet — a connector took them off it. Someone asks in the channel, and gets a link that works once, for them.
Get started
Set it up in four steps.
Install once, connect your LayerV account, choose what each channel can open. After that, asking is one message.
Anyone
Add it to Slack
Click Add to Slack and approve the permissions Slack shows you. If your workspace requires approval for new apps, ask a workspace admin.
Add to Slack →The first person
Connect your LayerV account
/qurl setup you@company.comRun this in any channel and sign in. Whoever connects first becomes the workspace owner and can add admins.
An admin
Choose what to share
/qurl-admin protectRun this in the channel that needs access. Choose qURL Connector to protect an internal app, or URL to share an existing link. It is available in that channel only.
Anyone in the channel
Ask for access
/qurl get $stats-dashboardReplace $stats-dashboard with the resource ID or alias from step 3. Or ask @qURL. The link works for the first person who opens it, then expires.
Stuck? In Slack, /qurl list shows what a channel can open and /qurl help lists every command. Or see the full command list.
How it works
Access is one message.
No new tool to learn. Ask for what you need the way you’d ask a coworker.
Stats dashboard
qurl.link/at_8xqp9h2- One-time use
- Expires in 10 min
- For alex@acme.com
Who it’s for
The same message works for people and agents.
People
A teammate who needs in — now.
- Nothing to install, no password to go find
- The link lands in the thread they asked in
- When it expires, so does their access
Agents
An AI agent finishing a task.
- One expiring path to one resource, not the network
- Nothing standing in the agent’s config to steal
- Same for APIs, databases, and MCP servers
Why it’s different
Only the person who asked gets in.
Nothing gets posted to the channel, and nothing goes back on the internet. One verified request opens the resource for one person, for as long as they need it. To everyone else, it still isn’t there.
- 1The resource is already hidden — a connector took it off the network.
- 2Someone asks the agent for it, in the channel they’re already in.
- 3Slack tells LayerV what was asked for, and who asked.
- 4Slack admins decide which channels and people can ask; the request is tied to the Slack identity that made it.
- 5They get a qURL to that one resource — nothing else on the network.
- 6It’s spent on first open, and expires either way.
Add private access to your Slack workflows.
Someone asks in the channel. They’re in seconds later, and the way in closes behind them.