An approval desk for the company data your AI agents ask for.

Agents connect to Ventport instead of to your HR system or database. Each request arrives with the exact fields, the people it covers and how long the answer will be kept. Whoever owns the data approves it, removes what isn't needed, or turns it down.

Set up your organisation Decide a request below

A request waiting for you

This is what an HR lead sees. Untick anything the agent doesn't need, then approve.

HR assistant, asking for the sales manager
Who in the sales team still has annual leave left? I'm planning the December roster.
Fields requested
Bank accountbank_accountRefused by policy
Covers the sales department, 9 people. Kept for 8 hours.

What the agent gets

Only what you approved, and only for the next two hours.

Nothing yet. Until someone approves, the agent has no access at all.

Wooden pinisi cargo ships moored along the quay at Sunda Kelapa, Jakarta, reflected in still water.
Pinisi at Sunda Kelapa, Jakarta's old harbour. Photo: Herusutimbul, Wikimedia Commons, CC BY-SA 4.0, cropped.

Why not just give the agent access?

Because a database login or an export answers every question the agent might ever ask, including the ones nobody would have approved. Ventport turns access into individual decisions: this agent, these fields, these people, for this long.

Team totals can be approved automatically by a policy, so routine questions don't wait for anyone. Anything about individual people waits for a person.

Rules that don't depend on who approves

Ventport doesn't keep the data
Rows go to the agent and nowhere else. The log records what was asked, who decided and how many rows left, never the values.
Some fields can't be asked for
Identity numbers, tax and bank details, salaries, addresses and health information are refused before a request reaches anyone.
Small groups stay hidden
A team total over one or two people would describe those people, so groups under three are left out.
An approval is for one request
It expires, and a request that changes a field, a filter or the audience needs a new decision.
Every step is on a tamper-evident log
Each entry is chained to the one before it, so a deleted or edited entry shows.
A closed wooden lock gate between stone walls on the Delaware Canal.
Lock 11, Delaware Canal. Photo: Zeete, Wikimedia Commons, CC BY-SA 4.0, cropped.

Connecting an agent

Ventport is an MCP server. Register the agent in Ventport, give it the token, and it can list what it may ask for, send requests, check on them and fetch approved results.

Every new organisation gets a sandbox of invented employees, so you can try the whole loop before connecting anything real. Enviera HRIS is the first real system it connects to.

A yellow mooring bollard with blue lines tied around it.
Photo: Lusi Lindwurm, Wikimedia Commons, CC BY-SA 4.0.
{
  "mcpServers": {
    "ventport": {
      "type": "http",
      "url": "https://app.ventport.com/mcp",
      "headers": {
        "Authorization": "Bearer <agent token>"
      }
    }
  }
}

Ventport is in early access. Setting up an organisation takes a work email and about two minutes.

Set up your organisation