Skip to content

See who was given access to a contact

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. Proven against quoxcli 0.6.2 on 2026-11-15.

Who had access to this contact?

Every time an agent is given a contact's details, ContactsQ issues a lease and records it. Ask Quox, and it reads that ledger for you.

What you get: the number of access leases issued for a contact, what each one released, who decided it and how often it was used, from ContactsQ’s lease ledger. The ledger records access, never the phone number or email themselves. You need: a signed-in profile. About 2 minutes.

The contact here is ContactsQ Selftest, the demo contact that ships with ContactsQ, on a scratch org.

quox · talking to Quox

Has anyone been given access to my ContactsQ Selftest demo contact's details? How many access leases have been issued for it?

▤ AOCL │ L1 identity complete · allowed · 0ms

▤ AOCL │ L3 policy gate complete · proceed · 3ms

◐ CONTACTS │ search ✔ CONTACTS │ search │ 1 candidates, ambiguous: false · 1.8s

⛓ AEE │ envelope opened · ops.tool · contacts_search ok

◐ QUOX │ cli ✔ QUOX │ cli │ 0 exit code, 4356 duration ms · 5.7s

⛓ AEE │ envelope opened · ops.tool · quox_cli ok

⛓ AEE │ envelope opened · stream_success

Yes. Two access leases have been issued for the ContactsQ Selftest (demo) contact, and
both were used.

Lease             cl_mwbhhgev_45dff99e3b40
Used at (UTC)     2026-11-11 02:12
What it released  Context: confirmed facts and interaction summaries

Lease             cl_mwccyl3y_06124a7e080f
Used at (UTC)     2026-11-11 16:53
What it released  Context: confirmed facts and interaction summaries

• Approval: the approval gate decided both leases.
• Scope: each was for the "service" purpose, any channel, and a single use. Each was
  used once and then expired.
• No phone or email released: both leases were context-only, so neither gave out the
  contact's phone number or email address. Those are shown only on the contact's
  ContactsQ page.
• Nothing outstanding: both leases are spent, and there have been no uses since 11
  November.

The lease ledger doesn't record which agent or person made each request. You can see the
contact's wider history on its ContactsQ page:
/contacts?contact=ct_mw44xrfv_2905b9fa2098.

17.6s · 2 tools · 0 approvals

A real turn on our own install (CLI 0.6.2, 15 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 15 Nov 2026 · test report mwh8m3

Quox made two calls: a contacts search to find the demo contact, then the lease ledger through its governed CLI tool. It reported two leases, both decided by the approval gate, both for the service purpose on any channel, each limited to a single use and each used once. Both were context only, so neither released the phone number or email. It also says plainly what the ledger does not hold: which agent or person made each request.

search
quox contacts search "ContactsQ Selftest"ID                          Name                         Kind      Status    Relationship    Identifiers                                Conf    Matchct_mw44xrfv_2905b9fa2098    ContactsQ Selftest (demo)    person    active                    phone:•••••••123 email:s•••@example.com    0.85    tokenⓆ CONTACTSQ │ contacts search │ 1 candidates
From a run on the same scratch org. Identifiers stay masked.
leases
quox contacts leases ct_mw44xrfv_2905b9fa2098id                          projection    channel    purpose    status    decided_by       uses    expires_atcl_mwccyl3y_06124a7e080f    context       any        service    used      approval_gate    1/1     2026-11-11T16:58:28.031Zcl_mwbhhgev_45dff99e3b40    context       any        service    used      approval_gate    1/1     2026-11-11T02:17:20.696ZⓆ CONTACTSQ │ contacts leases │ 2 leases
From the same run.

Each row is one lease: what it released (projection), for which channel and purpose, whether it is still open, who decided it, how many of its allowed uses were spent, and when it expired. A context lease releases facts and interaction summaries, not the phone number or email.

Quox did not guess who had seen the contact. It found the contact, then read the same lease ledger that quox contacts leases reads, and reported what came back. The conversation and the CLI agree: two leases, both used.

quox contacts leases only reads and raises no approval. Count the rows for your own contact and compare with what Quox told you. If they disagree, trust the CLI and tell us.

Nothing to undo: reading the ledger changes nothing. A lease is spent or expires on its own; the ledger keeps the record either way.