Console handbook
What every page of the TrustWix console does, and which one answers the question you have
The rest of this site is written for the developer who integrates TrustWix. This section is written for everybody else on your team: the person working the review queue, the manager watching the approval rate, the owner adding a colleague. It assumes you have never seen a line of our API and never need to.
The console is at app.trustwix.com. Every page in it has a job, and this handbook gives one page
of explanation to each: what you are looking at, what you can change, and what happens to an
applicant when you do.
Read this much first
Three ideas run through the whole console, and most confusion comes from missing one of them.
A verification is one attempt. Somebody starts a session, submits their document and their selfie, and it ends in a verdict. The Verifications page is a list of attempts. The Persons page is a list of people, each carrying every attempt they have made with you.
Sandbox and live are two separate worlds. Test traffic and real applicants never mix. The environment you are looking at is chosen in the sidebar, and it changes what nearly every page shows. See Environments.
What you can see and do depends on your seat. Roles are enforced by the server, not just hidden in the menu, so a page you cannot open is a page your role does not include. See Roles and permissions.
Find the page you need
| You want to | Go to |
|---|---|
| See how today is going | Overview |
| Look up one applicant and what happened to them | Verifications |
| See everything one person has ever done with you | Persons |
| Decide the cases the engine would not decide | Manual review |
| Understand how much work reaches your reviewers, and why | Analytics |
| Find out what your integration sent and what we sent back | Logs |
| See what you are being billed for | Usage |
| Change which checks an applicant goes through | Flows |
| Write the explanations reviewers send when they reject | Reason templates |
| Label cases for your own team | Tags |
| Give your developers credentials | API keys |
| Receive results at your own servers | Webhooks |
| Add a colleague, or change what they can reach | Team |
| See who on your team did what | Team activity |
| Change branding, security, and account-wide rules | Settings |
If you know the word but not the page, try the glossary. If something is happening that you did not expect, start at common questions.
Things that behave the same everywhere
Confirm it is you
Some actions ask for a code from your authenticator app before they go through. That is a step-up check, and it guards actions that expose a secret, reveal applicant identity, or change what other people can reach. It is not a sign that anything is wrong.
Pages that hold a form keep a save bar at the bottom while you have unsaved changes, and warn you if you try to leave with work in progress. Lists remember the filters you set while you move around inside them. The language of the console, and light or dark, are yours alone and set from the menu in the bottom of the sidebar; changing them affects nothing an applicant sees.
Viewing an applicant's name, date of birth, document or photographs is recorded against your name every time. That is deliberate, and it is what lets an owner answer the question of who looked at whose data.