Hummand presents

Dashboard

Where the client's team creates and follows each act, the receipt it leaves
and who opened what. No integration to get started.

dash.hummand.com.br available;
per-client orchestration available.

Dashboard · the side of whoever asks for the proof

Whoever uses it every day
sees the record.

The journey happens on the phone of the person being verified; the dashboard is the other side, that of the analyst and the supervisor who asked for the proof. There each act appears in the product's vocabulary, the receipt batch comes out exactly as signed to be verified elsewhere, mandates and alerts stay in view, and every opening of an act's evidence shows who opened it, when and why. The dashboard does not decide policy, level or verdict: it shows what the server returns. In Portuguese and English, in light and dark themes.A batch is a set of receipts exported at once; the evidence is the encrypted content of an act, which only opens with a declared reason and leaves a record.

Three areas,
one record.

Operations

`Acts`available

List and detail of each act: type, level, state, subject by the client's reference, steps in the server's order, mandate scope, chaining and minimised verdict
Filters by type, state, result, client reference and period, with the query total, the step trail in the list itself, CSV export and search from the keyboard shortcut
Tabs for campaigns, with the progress of each batch, for upcoming deadlines and for alerts
My queue: what needs action today, from acts with no answer to links about to expire, and the reverification cycles
Act dossier: the act, the timeline, the consents, the receipt and every access to the evidence, in a single document
Search by id, client reference, receipt hash or campaign name
Who opened the act's evidence, when and for what reason, with the hash link of each opening

`New verification`available

Creates the act through the same door as the API, among the types the policy executes, and generates the journey link: the person completes the steps on their own phone, with no integration
Batch campaign: a list of references pasted from a spreadsheet becomes acts with a common deadline, in parts of up to 500 that carry on as a single campaign, with a name, an owner, a report and a reminder of who is missing; the links come out as a CSV
Sandbox with a simulated result, outside the receipt chain, with a demonstration link for the journey, no camera and no record
The enrolment photo can be attached to each act after creation, in the batch too; with it, presence comes with match

`Receipts`available

List in chain order, with a period filter
Batch export exactly as signed, to verify outside Hummand
Evidence access receipts, with status and download, and the checkpoint of both chains
In the act detail, its receipt, the pending state or why there is no receipt

`Mandates`available

Mandates in force and ended, with who received the authority, allowed actions and validity, and a filter by grantee
Revocation with confirmation, when the mandate's scope allows it, and batch revocation with a count of what fell

`Alerts`available

Expired proof, act outside a mandate and expected act missing, computed on read from the acts and receipts

Reading

`Overview`available

Recent acts, verdicts and the review queue in one place, with the activity map of the past year
First steps of the integration for whoever is starting

`Metrics`available

Summary, conversion per step, attempts per subject, hours and latency per source
A free period, compared with the previous period of the same length

`Live`available

Wall screen for the control room: what is happening and what needs attention, over the last 24 hours and the last hour, refreshing on its own
Aggregates only, nothing that identifies anyone, and open to the analyst level

`Notifications`available

Act transitions as notifications, with preferences by channel and by type

`Orchestrations`available

Per act type: on or off, minimum level, deadline, attempts, required enrolment photo, context rules and reuse of a recent proof with passkey; every publication is a version
What is not executable yet is highlighted, with the missing step

Account and control

`Team and access levels`available

Invitation by a single-use set-password link
Access levels checked by the server, with a minimum of administrators that protects the company's own access; an administrator cannot change or remove another
The last activity of each person, to see who has access and does not use it
Auditor profile, which reads what the supervisor reads and writes nothing
Units in a tree: whoever is in a unit sees only the acts of that unit and the ones below it
Scheduled access review, in which the administrator keeps or removes each person

`Security`available

Two-step verification and recovery codes
Sign in with a passkey, SSO with Google, IP list for the dashboard and the API
Open sessions of the account, ending the others, and password change

`API keys`available

Creation, rotation and revocation, with test and production environments

`Webhooks`available

Endpoints with a rotatable secret, signed delivery, delivery log and test ping
Redelivery of an exhausted event, with the same event_id

`Audit`available

The trail of what the team did in the dashboard, with filters by period, person, type and outcome, the declared reason, the hash link of each entry and CSV export

`Billing`available

Usage for the period and invoices

`Privacy`available

Retention periods and the accepted consent version
Retention per type with a legal basis and preservation of an act or campaign under dispute
Erasure request by act, by reference or by verdict, with the effect reported record by record
What Hummand does not do here, declared: portability and erasure by CPF

`Support`available

Searchable help in the dashboard itself
Tickets with text and an image, answered by the Hummand team; the answer arrives as a notification

Dashboard

Who opened it is written down

Every opening of an act's evidence appears in the client's dashboard: who opened it, when and for what reason,
including when the one who opened it was Hummand.

See the documentation

No code to get started

The dashboard generates the link, the person completes the steps on their own phone and the act arrives here with its receipt.
The API integration comes later and lands in the same record.

Dashboard

Already a client? Sign in.

Access is by password and two-step verification, passkey or SSO with Google, with an optional IP list and the invitation made by your team.

1.0

Verify a receipt

Paste the JSON and the public key. No account, nothing sent: it runs in your browser.

Open the verifier

2.0

Talk to us

A technical conversation, straight with the people who build it, no sales script.

Contact

Dashboard

Whoever uses it every day sees the record.

Three areas,one record.

Operations

Actsavailable

New verificationavailable

Receiptsavailable

Mandatesavailable

Alertsavailable

Reading

Overviewavailable

Metricsavailable

Liveavailable

Notificationsavailable

Orchestrationsavailable

Account and control

Team and access levelsavailable

Securityavailable

API keysavailable

Webhooksavailable

Auditavailable

Billingavailable

Privacyavailable

Supportavailable

Who opened it is written down

No code to get started

Already a client? Sign in.

Verify a receipt

Talk to us

Whoever uses it every day
sees the record.

Three areas,
one record.

`Acts`available

`New verification`available

`Receipts`available

`Mandates`available

`Alerts`available

`Overview`available

`Metrics`available

`Live`available

`Notifications`available

`Orchestrations`available

`Team and access levels`available

`Security`available

`API keys`available

`Webhooks`available

`Audit`available

`Billing`available

`Privacy`available

`Support`available