Requests for access
People can ask for access they don't have, with a reason and how long they need it. You approve it for a while, or decline it. Nothing is let through until you approve, and approved access ends by itself.
How requests work
Requests for access are part of the Organisation plan. Instead of finding you some other way, and you changing the whole rules file for an afternoon's work, the person asks in the app.
They ask, from their own device
For one device, one service's devices or one gateway's office network, on the ports they need, for how long (an hour to 30 days), and why, in a few words. Their device signs the request. Ask for access
Every administrator sees it
Under Administer, Requests, on every administrator's computer, within a minute. The rings by the clock ask for attention while one waits.
You approve it for a while, or decline it
Approved access works from the device that asked, to what it asked for, until the time you choose. Then it ends by itself on every device. You can end it sooner.
A request on its own lets nothing through
Every device keeps enforcing exactly the access rules it had until an administrator approves. The person sees your answer in their window.
Answer a request, step by step
Here Dana Shah, on dana-laptop, has asked to reach the file server, files, for 8 hours, and Sam, who looks after Northwind Clinic, approves it. Use Next, or click what's highlighted.
The rings ask for attention
While a request waits, the rings by the clock are grey with an orange dot, and so are the network's own small rings in the window. Pointing at the rings says how many requests wait, and their menu has a line such as Northwind Clinic: 1 request for access waiting. Open MultiTunnel. Click the rings to open the window.
Open the network
The network's row says 1 request for access waiting for your answer. Choose Open › beside it.
Answer it
On the network's page, under Administer Northwind Clinic, choose Answer 1 request for access. It opens Administer, Requests.
Read it, and choose how long
Under Waiting for an answer, each request says what they want to reach, who asked and from which device, the ports, how long and why.
Approve for starts at what they asked for. Choose a shorter or longer time if you like, from an hour to 30 days.
Approve
Choose Approve…. Or choose Decline…: nothing changes, and they see it was declined.
You approve or decline what was asked, as it is. To give something different, write a rule. Access rules
Windows asks
Windows asks for permission. Choose Yes.
Go ahead?
MultiTunnel says what approving does, read from the network's own records: who asked, from which device, for what, why, and until when. Check it, and choose Yes.
Your PIN
Windows asks for your admin PIN, in its own window.
Allowed now
The request moves to Allowed now, with its end time. Within a minute every device in the network lets dana-laptop reach
fileson that port, and Dana's window says it was approved, until when. The rings by the clock are back in full colour.
Command line
On Windows, in Terminal (Admin), once you have set $mt and $st. On Linux, in a terminal. Before you start
List the network's requests, newest first, each with its number and its code:
& $mt access $st northwindsudo multitunnel access /var/lib/multitunnel northwind412 (code 3fa9c2d1) Dana Shah on dana-laptop asked, 2026-11-18 09:12, to reach device files on tcp/445 for 8 hours: "monthly figures"; waiting for an answer (lapses 2026-11-25 09:12)
Approve one by its number, for a time such as 8h or 3d, or leave the time out for what they asked for. MultiTunnel shows the request in words and asks you to confirm before it signs:
& $mt access $st northwind approve 412 8hsudo multitunnel access /var/lib/multitunnel northwind approve 412 8hDecline one:
& $mt access $st northwind decline 412sudo multitunnel access /var/lib/multitunnel northwind decline 412In a script, add -ask with the request's code, as access lists it, and -yes. The answer is then signed only if the request is still the one you listed:
& $mt access $st northwind approve 412 8h -ask 3fa9c2d1 -yessudo multitunnel access /var/lib/multitunnel northwind approve 412 8h -ask 3fa9c2d1 -yesEnd access early
- Open Administer, then Requests.
- Under Allowed now, choose End now… beside the access.
- Windows asks for permission, MultiTunnel says what will end, and Windows asks for your admin PIN.
Every device stops letting it through within a minute, and the person's window says it was ended early by an administrator. Requests that were declined, ended, ran out or were never answered stay listed under Answered and past, for the record.
Command line
On Windows, in Terminal (Admin), once you have set $mt and $st. On Linux, in a terminal. Before you start
& $mt access $st northwind end 412sudo multitunnel access /var/lib/multitunnel northwind end 412What approving does
It adds one access rule
From the device that asked, to what it asked for, on those ports, until the time you chose. The person's other devices aren't included: from another device, they ask from that one.
It ends by itself
Every device stops applying it at that time, within a minute, with nothing more for you to do.
A service means its devices, now and later
Approving a request to reach a service lets the device reach the service's devices, including any added to it while the approval lasts.
Loading a new rules file replaces every rule, approvals in force included. To keep one, copy it into the file as devices shows it, with its "request" number. A rule with a request number is accepted only exactly as approved, and only while the approval lasts. Write and load your rules
Before you change a gateway's office network (set-route), MultiTunnel lists the approvals to it in force.
Command line: see approvals among the rules
On Windows, in Terminal (Admin), once you have set $mt and $st. On Linux, in a terminal. Before you start
& $mt devices $st northwindsudo multitunnel devices /var/lib/multitunnel northwindLimits, and what you'll see in Activity
- Each device can ask 3 times a day, and have up to 3 requests waiting. The same request can't be asked twice while one waits.
- A request nobody answers within a week lapses. It can't be approved then: they ask again.
- An approval lasts at most 30 days. For longer access, write a rule.
- A reason is up to 140 characters. It is kept in the network's records, which its devices hold, so people are told not to put passwords or private details in it.
- A service's devices can't ask: give them access in the rules.
- Requests need every device in the network to run a MultiTunnel that knows them. Until then, asking is refused, with the devices to update.
- A device that keeps asking for things it shouldn't can be removed, which ends its requests too. Remove a device
Every request and every answer is in Activity, such as Dana Shah asked, from dana-laptop, to reach device files on tcp/445 for 8 hours: “monthly figures”
, and Approved Dana Shah's request 412, from dana-laptop, to reach device files on tcp/445, until 18 Nov 2026 17:20 UTC
. A request is credited to the device that asked, by its ID, and an answer to the administrator's key. Activity and the audit trail
Still stuck?
Email us and a person will reply. For a security problem, write to security@multitunnel.co.uk instead.