Communities
Getting started
Set up a workspace for your community, invite your staff and run your first PC check.
1. Create an account and get a license#
Create an account on the registration page. There is no online checkout yet: licenses are issued by the DUXAC team. Once your license is issued you receive a license key in the format DUX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX.
2. Attach the license (your workspace)#
In the dashboard, use Add a license key in the workspace switcher and paste the key. The license becomes a workspace for your community, and you become its owner. The key is shown only when it is issued or rotated; keep it somewhere safe. If it leaks, the owner can rotate it from the workspace settings.
You can belong to several workspaces (for example if you are staff in more than one community). The workspace switcher at the top of the sidebar selects the one you are working in.
3. Invite your staff#
Under Members, invite people by the email address of their existing DUXAC account (they register first). Your plan sets the number of seats. Each member has one role:
| Role | Capabilities |
|---|---|
owner | scans.create, scans.review, scans.delete, players.write, signatures.write, members.write, settings.write, license.manage |
manager | scans.create, scans.review, scans.delete, players.write, signatures.write, members.write, settings.write |
staff | scans.create, scans.review, players.write |
4. Adjust the consent screen (optional)#
Under Settings you can set:
- Consent text: shown to the player before anything is scanned. If you leave it empty, the DUXAC default text is used.
- Default request note: a short explanation shown with the request, for example "Requested by the staff team after a report".
The consent screen always also lists every check with the data it reads; that list cannot be hidden.
5. Create a scan#
Under Scans, choose New scan, enter a label for the player (their in-game name or Discord tag; it is only for your staff) and an optional note. You receive a PIN like 7KQ4-M2XA. Give it to the player together with a link to the download page.
The PIN is shown once and expires. Every created scan counts against your plan's monthly quota.
| Limit | Value |
|---|---|
| PIN | 8 characters from 23456789ABCDEFGHJKMNPQRSTUVWXYZ, shown as XXXX-XXXX |
| PIN validity | 15 minutes |
| Time to answer the consent screen | 10 minutes |
| Time to complete an accepted scan | 30 minutes |
| Signature clock skew | ±120 seconds |
| Nonce memory | 300 seconds |
| Findings per upload batch | 200 |
| Findings per scan | 2000 |
| Evidence per finding | 4096 bytes of JSON |
| Signatures per scan config | 20000 |
6. Follow and review#
A scan moves through pending (waiting for the PIN), claimed (PIN entered, consent screen shown), running (consent given) and completed. It can also end as declined, expired, cancelled or failed. With live progress you see each check as it runs. When it completes, open the report and set a review status: see Verdicts & review.