← Integration Hub

PAXX

Built inBuilt inMOCK

Internal projects and approval candidates.

How it connects
Built in
Health
healthy
Integration status
connected
Credential
Not configured
Last sync
never
Connected
not yet

1 of 1 steps done

Setup

  1. Nothing to set up

    Done
    Nothing to doAutomatic

    PAXX's own data is built in. There is no account, key or authorization involved.

Built in

Connect

Live check

Connection test

This provider declares no connection test — it makes no external call, so there is nothing to probe and a green result here would mean nothing.

0 declared

Permissions

What PAXX asks the provider for. The provider's own consent screen is the authoritative grant — this list is what will be requested, and after connecting, what was actually returned.

No permissions needed.

Capabilities

What you get

  • Internal projects

    readNot available

    Projects PAXX tracks itself, independently of any external system.

    Available once this provider is connected.

    Dashboard → Projects

  • Approval candidates

    readNot available

    Derived candidates for the approvals queue.

    Available once this provider is connected.

    Dashboard → Approvals

Requirements

Diagnostics

Administrator requirements

One-time work for whoever administers this PAXX instance.

None.

Your requirements

Per-person steps — the authorization is yours, not the deployment's.

None.