Skip to main content
← All guides

Let only your company’s email addresses open an internal dashboard

Why qURL here

Everyone with a verified mailbox in your company domain reaches the dashboard and a mailbox in any other domain is refused, with no VPN client and no public URL. You set it up from the server’s terminal in one publish command.

See how LayerV compares to a VPN →

Steps

Install the qURL™ CLI on the server that runs the dashboard and publish it with a public name and the email-domain policy for your exact company domain. Colleagues open its qurl.link address, verify a mailbox in that domain, and get in; any other email is refused. The dashboard keeps listening on 127.0.0.1, with no VPN, no open port and no public URL.

  1. Install the qURL CLI on the server

    Run this in an SSH session as the user who will keep the share. It is the qURL skill’s installer: it checks the download against the release checksums and installs into ~/.local/bin, with no sudo. Add the export line to ~/.bashrc or ~/.zshrc so later sessions find qurl.

    (umask 022 && mkdir -p "$HOME/.local/bin" "$HOME/.local/state") &&
      chmod go-w "$HOME/.local" "$HOME/.local/bin" "$HOME/.local/state" &&
      installer=$(mktemp) &&
      curl -fsSL --retry 3 --proto '=https' -o "$installer" \
        https://raw.githubusercontent.com/layervai/qurl-integrations/main/scripts/install.sh &&
      INSTALL_DIR="$HOME/.local/bin" sh "$installer" &&
      rm -f "$installer"
    export PATH="$HOME/.local/bin:$PATH"
    qurl --version

    Check: The last line prints 4.0.0 or later.

  2. Turn on lingering for your user, once

    qurl publish installs its background service as a systemd user service. systemd starts your user manager when you log in and stops it, with every user service, a few seconds after your last session ends; lingering keeps it running and starts it at boot. Where polkit runs, as on Ubuntu cloud images, systemd’s default policy lets you turn lingering on for yourself, with no sudo. Without polkit, as in many minimal images, the command answers “Access denied”, and an administrator runs sudo loginctl enable-linger with your user name. The second line should print Linger=yes.

    loginctl enable-linger
    loginctl show-user "$USER" --property=Linger

    Check: The second command prints Linger=yes.

  3. Keep the dashboard on the server’s loopback address

    Set the dashboard to listen on 127.0.0.1 instead of every interface; its documentation names the setting. Check from the server that it answers on that address. qURL connects to it there, so it needs no port open to your network or the internet.

    curl --fail http://127.0.0.1:3000/

    Check: curl prints the dashboard’s page and exits without an error. If curl says it couldn’t connect, start the app first, or use the port it runs on.

  4. Publish it for your company email domain, with a name

    Use the exact domain in lowercase. It does not include subdomains or other domains, so mail.example.com is a separate domain. People verify a mailbox in that domain before they get in. The name shows on the access page and in the verification email; it is public text, so keep secrets and internal notes out of it. The background service keeps serving after you log out and comes back after a reboot. Publishing the same address again must confirm the same domain; it never changes the policy silently.

    qurl publish http://127.0.0.1:3000 \
      --access email_domain --email-domain example.com \
      --name "Team metrics" -o json

    Check: The reply says private: true and its consumer_access names the email-domain policy with your domain. The reply also says found_existing: false. If it says true, this address was already shared with the same policy, and qURL gave you that earlier link; if it was shared with another policy, publish refuses with “existing consumer policy differs”. Either way, publish again with --id and a new ID to make a separate link. Save the CRID and the address it returns.

  5. Confirm the dashboard is serving

    A successful publish does not prove the route is up. Read the resource’s status before anyone opens the address.

    qurl status <CRID> -o json

    Check: connection_state is "serving". For any other state, run qurl inspect <CRID> -o json to see why.

  6. Test with a mailbox in your domain

    Open https://qurl.link/<CRID> in a browser with no session, verify a mailbox in your domain, and click through the dashboard’s pages.

    Check: The dashboard opens, and its own sign-in still applies.

  7. Test with a mailbox outside your domain

    Open the same address in another browser with no session and try a mailbox in any other domain, such as a personal address.

    Check: That mailbox is refused, and the dashboard never loads.

  8. Share the address with your team

    Post the full https://qurl.link/<CRID> address where your team finds it. The address of a private resource is safe to send to anyone, because it opens nothing for a mailbox outside your domain.

  9. Close any old public route

    Publishing with qURL does not close a route the dashboard already has. Remove public port mappings, firewall openings, load balancer rules and DNS records that still reach it, and keep the dashboard’s own sign-in and roles for what each person may do.

    Check: From a machine outside your network, the dashboard’s old public address no longer answers.

  10. Remove someone who leaves the company

    An existing grant stays active until you remove it, even after their mailbox is disabled. Disable the mailbox to stop new verification, list the grants, and remove theirs with its grant ID and current version.

    qurl access list_grants <CRID> -o json
    qurl access revoke_grant <CRID> <grant-id> \
      --version <current-version> -o json

    Check: session_cleanup in the reply is complete. If it says pending, run the same command with the same version again until it is complete.

  11. Change the domain later

    Read the resource’s current policy version first, then configure the new domain with it. The service stores the next version. If the reply says session removal is pending, run the same command again.

    qurl list --status active -o json
    qurl access configure <CRID> --mode email_domain \
      --email-domain example.com --version <current-version> -o json

    Check: The reply names the new domain. On a version conflict, read the current version again; never increment it yourself.

What the recipient sees

A colleague opens the qurl.link address and sees the dashboard’s name and who published it.

More

They agree that the publisher receives their verified email, verify a mailbox in your domain, and save a passkey; the page can also offer to email them an access link instead. Then they reach the dashboard, where its own sign-in still applies. A mailbox in any other domain is refused.

Which walkthrough fits who should get in

Pick the row that matches who should reach the app.

Which walkthrough fits who should get in
Who should get inWalkthrough
People who ask, after you approve each oneLet a client request access to your app, and approve them
Only the email addresses you name, with no requestsGive a contractor temporary access to your app
Anyone with a verified mailbox in your company domainThis guide
Buyers who pay through StripeCharge for access to an app

Troubleshooting

Troubleshooting
If you seeDo this
qurl publish does not accept --email-domain or --nameRun qurl --version. This walkthrough needs 4.0.0 or later. Run the installer again to update. If the server still refuses the policy, keep the dashboard private.
qurl status does not report connection_state "serving"Run qurl inspect <CRID> -o json for the reason. Check that the dashboard still answers on 127.0.0.1 with curl, then run qurl start <CRID>.
Show 4 more fixes
More troubleshooting
If you seeDo this
A colleague on a subdomain address is refusedThe domain match is exact: team.example.com is not example.com. Publish a separate resource for that domain, or ask them to verify a mailbox in the domain you set.
The share stops a few seconds after you log outLingering is off for your user. Run loginctl enable-linger, check that loginctl show-user prints Linger=yes, and publish again: it reuses the same CRID.
qurl publish says the local app is not accepting TCP connectionsStart the app first and check that curl works on the same address. qurl publish connects to localhost as 127.0.0.1, so if your app listens only on IPv6 (on macOS or Linux, lsof -iTCP -sTCP:LISTEN -nP shows [::1]), publish 'http://[::1]:PORT' instead, or start the dev server with --host 127.0.0.1 and publish that address. Neither requires listening on your LAN. Keep the quotes: zsh treats the brackets as a pattern.
publish says this Linux session “can’t reach a systemd user manager”You are in a container or sandbox without a user service manager. Run qurl publish with --foreground; sharing lasts as long as that process runs. Container and CI setup →

Frequently Asked Questions

How do I share a Grafana or Metabase dashboard with my team without a VPN?

Keep the dashboard on the server’s loopback address and publish it with qurl publish --access email_domain for your company domain. Teammates open its qurl.link address in a browser and verify their work email; no VPN client, open port or public URL is involved.

Can a coding agent on the server run this walkthrough?

Yes. Paste the agent prompt above into an agent that can run commands in an SSH session on the server. It turns on lingering, publishes with the email-domain policy and a name, and checks the reply and the serving status before it gives you the address.

Do colleagues need a LayerV account or a VPN client?

No. They need a browser and a mailbox in your company domain. They verify it and save a passkey the first time.

Does this replace the dashboard’s own sign-in?

No. The email-domain policy decides who can reach the dashboard. Its own accounts and roles still decide what each person can see and change.

Is the access anonymous?

No. The publisher receives each person’s verified email, and they agree to that before they verify. Mailbox verification shows control of an address, not legal identity.

What if the server has no systemd user manager, as in a container?

Run qurl publish with --foreground as a background job. The share then lasts as long as that process runs, so supervise it the way you supervise the dashboard.

What happens when someone leaves the company?

Their existing grant stays active until you remove it, even after their mailbox is disabled. Disable the mailbox to prevent new verification, then remove their grant as shown in the step above.

How do I rename the dashboard after publishing?

Run qurl preview set <CRID> --name with the new name. Publishing the same address again keeps the name it has.

Can someone on the same network reach the app?

Network admission can include devices that share the same public IP address as an admitted visitor. The private browser origin also requires a valid access grant for that visitor. Keep your app’s own sign-in and permissions to control what each person can do.

Publish your dashboard for your team

After the loopback check passes, publish it with your company email domain and a name.

Or use the CLI →

Book a pilot

Tell us what to hide. We’ll scope a pilot.

Enterprise starts with a paid pilot on one application, typically 60 to 90 days, credited in full toward year one if you convert within 60 days. After that, an annual package sized to what you protect, not per seat.