Credentials On The GO — Client Administrator Guide

Audience: company administrators responsible for employee profiles, training requirements, evidence review, and employee app access.
Product stage: pilot preparation and internal device testing.
Guide revision: October 12, 2026 — employee certificate export added. Features require their matching deployed website or installed mobile build; this guide alone does not update either.

This guide covers the office workflow from company setup through offboarding. It describes the behavior already implemented in the Credentials On The GO client workspace. Features described as planned must not be promised as available.

September 23 update: the starting catalog is selected during company onboarding. Choosing a primary industry loads its suggestions; changing it clears the previous draft selection. Other starts empty for manual selection. Company administrators can add definitions from other industries later; administrators and clerks explicitly assign baseline or site requirements to selected employees. The employee app remains read-only. Complete physical-device field acceptance remains a separate release check.

What a client administrator controls#

A client administrator can:

• update company identity, office contact, time zone, and renewal warning window;
• create and manage administrator, clerk, and viewer office accounts;
• maintain the company training catalog and job-role requirement groups;
• add employees individually or import a validated CSV roster;
• export the company roster and certificate history as CSV;
• maintain employee details and photographs;
• assign requirements and add certificate or training evidence;
• approve, reject, renew, or revoke credential records;
• create, reset, disable, and revoke employee-app access;
• review dashboards, attention items, and the activity log; and
• control the information the company publishes to employee wallets and auditor views.

A client administrator does not certify an employee on Provider's behalf. The company remains responsible for its training policies, evidence standards, approvals, retention, employment decisions, and site-access representations.

Office roles#

Use the lowest role that lets each person do their job. Review office access at launch, monthly during the pilot, and immediately after a role or employment change.

Pilot launch checklist#

Governance and policy#

• [ ] Name one executive sponsor, one primary company administrator, and one backup administrator.
• [ ] Approve the authoritative training list and job-role matrix.
• [ ] Confirm which evidence is acceptable for each training item: certificate file, dated checkoff, or another documented method.
• [ ] Confirm completion-date and expiration-date rules. Do not invent expiration periods.
• [ ] Name the people authorized to approve, reject, and revoke records.
• [ ] Define how employees request corrections and how quickly the office responds.
• [ ] Define offboarding, retention, legal-hold, and deletion rules with employment and privacy counsel.
• [ ] Approve the fields an auditor may see after a QR scan.

Technical readiness#

• [ ] Production uses a separate HTTPS origin, database, restricted database user, and private file storage.
• [ ] Production configuration passes php bin/check-config.php.
• [ ] Backups run automatically and a full restore has been demonstrated.
• [ ] The EULA, Privacy Notice, Customer Services Agreement, and workforce notice are approved and published.
• [ ] Physical iPhone and Android acceptance testing is complete.
• [ ] At least two administrators can sign in, reset access through the approved process, and reach support.
• [ ] The pilot support and incident contacts are documented.

Data readiness#

• [ ] Roster has unique, final employee numbers.
• [ ] Duplicate names and employee numbers are resolved before import.
• [ ] Photos are authorized and suitable for identification.
• [ ] Historical evidence is readable and matched to the correct employee.
• [ ] The first dashboard reconciliation is compared with the company's source records.

1. Sign in safely#

Choose your language#

Use Language to choose English, Español, Français, Ελληνικά or Italiano. The office website remembers the choice in that browser; the employee app remembers its own choice on the device. Switching language keeps your current company, form entries and records. If no choice is saved, a supported browser/device language is used, otherwise English.

The selector translates interface controls and instructions. Names, company-entered text, training titles and uploaded certificate documents retain their original wording. This guide and the legal documents are currently provided in English, with translated navigation and an explanatory notice. Service emails still use English templates.

Open the final company login URL over HTTPS. Use the office account created for you; employee-wallet credentials are separate.

1. Enter your work email and password.
2. Confirm the company selector shows the company you intend to manage.
3. Before every upload, approval, or account change, recheck the selected company.
4. Sign out when finished on a shared device.

Sessions currently end after 30 minutes of inactivity or 12 hours total. A password change invalidates other sessions. If another tab changes the selected company, stale tabs are prevented from saving into the wrong company.

There is no self-service password recovery, email invitation, or multi-factor authentication in the current release. Use the approved administrator/support process. Never send passwords and usernames together in the same insecure message.

2. Complete Company setup#

Open Company setup and enter:

• the full company name employees and auditors should recognize;
• the approved brand color;
• office contact email and phone;
• a short welcome message, if desired;
• the number of days before expiration that should count as Expiring soon; and
• the company's operating time zone.

The time zone affects dashboard dates and expiration calculations. An approved credential remains current through its expiration date in the configured company time zone.

The warning window changes when an item appears as Expiring soon. It does not change the underlying certificate date and does not send automated reminders in the current release.

3. Establish Office access#

Open Office access.

1. Create a separate named account for each office user.
2. Assign administrator, clerk, or viewer based on the person's responsibilities.
3. Deliver initial credentials through the company's approved secure channel.
4. Ask the user to sign in and change the temporary password immediately.
5. Record the access approval outside the application if company policy requires it.

Do not create shared office accounts. Disable access immediately when a user changes roles or leaves. Keep two active administrators so one account does not become a single point of failure.

4. Review the Training catalog#

Each new company begins with the definitions reviewed during onboarding. Choosing a primary industry loads its suggestions automatically; changing it replaces the draft selection, including custom entries. Other starts empty for a custom selection, or the owner can explicitly defer training setup. No separate CCI button is needed. Existing companies retain their catalog. New employees start unchecked; adding a catalog item does not make it mandatory for anyone.

Your primary industry helps suggest starting content. It does not restrict access to other shared lists. An administrator can update primary/additional industries in Company setup; that changes metadata only and preserves the catalog, assignments and proof.

Add training from another industry#

1. Open Training catalog → Browse training library as a company administrator.
2. Choose All industries or another industry filter. Search names, tasks and sources.
3. Select the relevant definitions. Select all shown and Clear shown affect only the visible results. Clear all selected removes the entire shared selection. Filters preserve existing choices.
4. Inspect the type, source, applicability and unconfirmed-policy labels. CCI role suggestions are reference information, not assignments. Add a company-specific requirement when needed; private additions are not published to other clients.
5. Choose Preview catalog changes. Review additions, existing canonical matches and any name conflicts. Existing company entries are kept unchanged. Resolve a conflict by removing the selection or giving a genuinely different qualification a distinct display name; a similar name alone does not establish that two credentials are equivalent.
6. Confirm the review and choose Apply reviewed changes. Then assign requirements separately to the appropriate employees.

The first shared publication offers 67 definitions: 41 CCI names and 26 selected industry families. Starter lists are suggestions, not complete regulatory programs. All expiration policies require company confirmation. Source references and CCI role suggestions are available in item details. A library update does not silently overwrite the company's accepted version or edits.

For every catalog item, confirm:

• display name;
• whether it applies to all employees or only a job-role group;
• whether supporting evidence is required;
• whether the item expires, never expires, or has an unconfirmed policy; and
• the source of the company's policy.

Do not mark an item non-expiring merely because no expiration date is currently available. Use the unconfirmed state until the company approves a policy.

Requirement groups#

On the employee profile, check the applicable baseline classes and choose Save baseline requirements. Select all baseline and Clear baseline selection help edit the list; saving makes the change effective. Existing baseline selections remain checked until explicitly saved otherwise. Clerks and administrators can add or remove them; the change is audited and earlier certificates/files remain in history. Requirements from an active site assignment are shown separately and remain active even when not selected in the baseline checklist. The checklist does not implement a separate waiver approval process.

Changing a job role/profile or uploading evidence does not assign requirements automatically. Explicit administrator requirement-group assignment remains available for matching existing employees. Review those bulk selections before applying them.

Before importing employees, reconcile group names with the job-role values in the roster. Spelling differences create operational confusion even when the import itself succeeds.

Assign an occasional site visit#

1. Confirm the destination site's actual requirements, issuer/scope and acceptance rules. Add any missing definitions to the company catalog first.
2. Open Site assignments and choose Assign a site visit. Company administrators and clerks can do this; viewers and employees cannot.
3. Optionally enter a site/project label and visit dates. Select only the visiting employees and the requirements they need. Every selected employee receives every selected requirement shown in the review.
4. Choose Review assignment, check the names and classes, then Confirm assignment. Other employees are unchanged. Existing approved evidence for that training remains available; confirm its scope and the site's acceptance before relying on it.
5. After the visit, use Close assignment, enter the reason and confirm closure. Turn on Include closed assignment history to see the retained record.

Visit dates describe the assignment. They do not change a certificate's expiration or automatically close the visit. Closing one assignment removes only its requirement reason: baseline requirements and other active visits remain effective. Earlier certificates, dates and proof stay in office history. A site-only requirement drops out of the current employee wallet/auditor summary when its last active reason closes; the underlying evidence is preserved.

The same requirement appears once in the wallet even when needed by more than one assignment. Catalog selection, proof approval and site acceptance are separate decisions. A saved site assignment does not certify the employee or authorize site entry. To change the people or requirements of a saved visit, deliberately close it and create a replacement; its original history remains.

5. Prepare and import the employee roster#

The CSV import creates new employees only; it does not update existing profiles.

1. Open Employees and select Download template beside Import CSV. The same download is available inside the import dialog.
2. Open the CSV in Excel or another spreadsheet app. Replace the sample employee; keep the column headings unchanged.
3. Enter one employee per row. Employee number and name are required; set active to 1 (active) or 0 (inactive). Other fields are optional. Use unique, final employee numbers. Format employee numbers and phone numbers as text to preserve leading zeros.
4. Save as CSV UTF-8 (comma delimited). The current limit is 1,000 employees and a file smaller than 2 MB.
5. Select Import CSV, choose the saved file, and review every validation result.
6. Correct the source CSV and preview again until there are no errors.
7. Commit the import.

The batch saves transactionally: if the commit fails, it does not intentionally save a partial roster. New employees start with no selected requirements. Select and save each employee's applicable classes before treating their wallet as ready.

Clean-roster rules#

• Do not use Social Security numbers as employee numbers.
• Do not reuse the employee number of a former employee.
• Use the employee's normal display name and confirm any legal-name requirement with company policy.
• Standardize role, location, and unit names before import.
• Remove blank trailing rows and spreadsheet formulas.
• Keep the import source file in the company's approved secure records location.

Export employees and certificate records#

Company administrators can open Employees and select Export employees & certificates. The CSV includes every employee in the selected company, including inactive employees and people without certificates; the page's search and status filters do not limit the export.

There is one row per certificate history record. Assigned training without a record gets a row marked Certificate record added: No. Employees with neither assignments nor records still appear with blank certificate fields. The report includes employee number, name, role, location, unit, certificate title, approval state, dates, and whether a proof file was uploaded. It includes proof filenames, not the certificate files themselves. Historical certificates remain listed even when no longer assigned.

Current requirement status describes the assigned requirement across its records. Record approval status describes the individual history row; a pending renewal can therefore appear alongside an approved certificate while the requirement remains current. Added records or uploaded files alone do not establish approval. Baseline and active-site columns show why an item is currently required.

Headings and status labels follow your selected interface language; employee names, training titles and filenames retain their original text. Dates use year-month-day and timestamps use UTC. In Excel, use Data > From Text/CSV, choose UTF-8 and a comma delimiter, and import employee numbers and record IDs as text if leading zeros must be preserved. Text that could be interpreted as a spreadsheet formula is prefixed with an apostrophe in the export. This report is separate from the employee import template.

6. Finish each employee profile#

Open the employee from Employees and confirm:

• employee number and name;
• job title or role;
• location, yard, division, or unit;
• company status: active or inactive;
• authorized profile photograph; and
• assigned requirements.

Photos accept actual JPEG or PNG data. Certificates accept JPEG, PNG, or PDF. Individual uploads are limited to 10 MB and images to 40 megapixels. Files are stored in private paths and served only after authorization.

The platform does not currently scan uploads for malware or re-encode images. Office staff should upload only known business records from trusted sources.

7. Add credential evidence#

For each training or certificate record:

1. Select the correct requirement.
2. Enter the completion or issue date from the evidence.
3. Enter the expiration date exactly as the company policy and evidence support, or explicitly record that the credential does not expire when that policy is confirmed.
4. Enter issuer or notes when useful.
5. Upload the certificate image/PDF, or use the approved checkoff workflow when an attachment is not required.
6. Save the record for review.

Never change a source certificate to make it appear current. Renewal creates a new version and preserves earlier history.

8. Review and approve evidence#

Open Review queue. For each pending record:

1. Confirm the employee identity and requirement.
2. Download and inspect the supporting evidence when present.
3. Compare the displayed issue and expiration dates with the evidence.
4. Confirm the issuer and evidence type meet company policy.
5. Approve the record, or reject it with a clear correction reason.

Only approved evidence should be published to the employee wallet and auditor view. Rejections and revocations require a reason. Do not approve your own uncertain entry merely to clear the queue; escalate to the designated policy owner.

Status meanings#

A pending renewal does not erase the earlier approved version. The current approved version remains available until it expires or is revoked.

9. Reconcile the Overview dashboard#

The dashboard counts active employees and their assigned requirements. It shows active employee count, requirement readiness, expiring items, pending reviews, and an attention list.

Readiness is based on assigned requirements, not a legal compliance determination. A company with no requirements shows no percentage rather than 100%. The attention list is an operational queue and may show up to 30 matching items; open the employee for full history.

During the pilot, reconcile the dashboard against the company's authoritative records:

• after the initial import;
• after a bulk evidence load;
• weekly during the first month; and
• before any executive or customer-facing report.

Record and resolve differences rather than adjusting source data to force a percentage.

10. Set up employee app access#

From the employee profile, a company administrator can set up or reset the employee's separate application access, disable that access, and revoke active device or QR authorization.

1. Confirm you are on the correct employee profile.
2. Create or reset the employee app credential using the approved workflow.
3. Deliver the company ID, employee number and office-issued password securely. Mobile version 0.1.1 labels the field Employee ID; it authenticates by employee number, not office email or a separate username.
4. Have the employee sign in on their own device. Employee password changes/resets currently require the company administrator; the app has no self-service password-change screen. Office users' My account password control is a separate feature.
5. Confirm the Who I am profile and credential list are correct.
6. Confirm the employee can open a credential and return to the wallet.
7. Confirm device authentication works only after normal sign-in has established the protected session.

Face ID, Touch ID, or Android biometrics are performed by the device. COTG should receive only an authentication success/failure result. The employee can use the supported password method instead. Face ID testing requires a signed iOS development or distribution build; Expo Go does not validate the full production Face ID flow.

11. Test the auditor QR workflow#

Normal production use creates a revocable link with the displayed short expiration, currently 15 minutes.

1. Employee signs in to COTG and opens the QR action.
2. Employee confirms the on-screen sharing explanation.
3. Auditor scans the code with a separate phone.
4. Auditor's browser opens the company-published summary without an auditor account.
5. Confirm the employee identity, company, timestamp, statuses, and approved evidence match the office record.
6. Let the link expire and confirm it no longer opens.
7. Create another link, revoke it from the office workflow, and confirm it stops working.

The non-expiring QR used on the public pre-alpha is only for explicitly allowlisted fictional test identities. Production's default allowlist is empty. Never enable a permanent QR for a real employee.

An auditor result is a current company record, not an independent certification or promise of site admission. Employees should keep any physical proof required by a regulator, site, collective bargaining agreement, or company policy until the company formally confirms the digital record is accepted.

12. Renew, reject, revoke, and correct#

Renewal#

Add the new evidence as a new credential version. Verify the new issue and expiration dates, then approve it. Preserve the earlier version for history according to company retention rules.

Rejection#

Reject unreadable, mismatched, incomplete, altered, unapproved, or policy-noncompliant evidence. Enter a reason that tells the submitter what must be corrected without exposing unnecessary sensitive data.

Revocation#

Revoke approved evidence when the company determines it should no longer be relied upon. Use the actual reason and follow the company's authorization policy. Revocation is different from expiration and should be rare and traceable.

Correction#

Correct factual profile errors promptly. For evidence changes, preserve history rather than overwriting the prior reviewed version. If the correction affects an active auditor share, revoke the share and have the employee generate a new one after the correction is approved.

13. Offboard an employee#

Complete these steps as part of the company's offboarding process:

1. Set the employee inactive.
2. Disable employee application access.
3. Revoke active device and QR authorization.
4. Confirm no office account was created for the person unless separately required; disable it if one exists.
5. Preserve, export, or delete records according to approved retention, legal-hold, employment, and privacy rules.
6. Record the action in the company's offboarding evidence.

Inactivation removes the employee from active dashboard calculations. It does not automatically decide whether records should be deleted.

14. Activity log and oversight#

Use Activity log to review important office and security actions. During the pilot, administrators should review it weekly and after any suspected issue. Escalate unexpected company selection, account changes, approvals, revocations, downloads, or access resets.

Application audit history supports investigation but does not replace the company's HR, safety, training, or legal records.

15. Integrations#

The Integrations area currently records planning information only. It does not connect to Paycom, Samsara, QuickBooks, DMX, Dossier, or another provider, and it does not store third-party secrets.

Do not place production third-party credentials in notes, browser fields, spreadsheets, or source files. A future integration must use a separately reviewed server-side adapter, least-privilege credentials, audit logging, and an agreed source-of-truth policy.

16. Security and incident response#

Immediately contact the designated company administrator and pilot support contact if:

• an unauthorized person can see a profile or certificate;
• a QR link opens after expiry or revocation;
• a file appears under the wrong employee or company;
• a device, password, administrator account, or exported file is lost or compromised;
• malware or an unexpected file is uploaded;
• the system sends a record to the wrong recipient; or
• production is unavailable during a required field check.

Preserve relevant timestamps, employee number, affected screen, device type, browser/app version, and a screenshot that does not unnecessarily expose other employees. Do not investigate by downloading more personal data or sharing the issue in a public channel.

The company and Provider incident leads determine containment, notification, restoration, and legal obligations. Administrators should not promise a breach notice or legal conclusion on their own.

17. Routine operating schedule#

Daily#

• Review pending evidence and urgent expired items.
• Process reported corrections and access problems.
• Disable known departing users promptly.

Weekly#

• Review expiring and missing items.
• Review the activity log during the pilot.
• Reconcile a sample of dashboard records with source evidence.
• Confirm the backup job completed.

Monthly#

• Review office accounts and roles.
• Review inactive employees and offboarding completeness.
• Review catalog policies and unconfirmed expiration rules.
• Test an employee login and QR expiry/revocation on iPhone and Android.

Quarterly or after a material release#

• Perform a restore drill or the agreed restore-test schedule.
• Revalidate the EULA, Privacy Notice, app-store disclosures, data map, subprocessors, and retention rules.
• Review accessibility and security test results.

Frequently asked questions#

Is there a Billing & Subscription page?#

It is planned and is not available in the current pilot. The requested page will show the company's plan, billable employee count, trial or renewal date, upcoming amount, invoices, receipts, payment methods and cancellation controls. Billing access is intended for authorized company administrators; employees and auditors will not see company financial details.

Will we receive a notice before payment is due?#

Yes, advance renewal/due notices and failed-payment follow-up are required for the commercial release, but automated billing emails are not active yet. Final timing, billing contacts and any grace period will be shown in the customer's agreement and billing settings. Training-expiration warnings are a separate feature.

What payment methods are planned?#

Credit and debit cards, US bank debit, and eligible Apple Pay/Google Pay website checkout are proposed. Availability depends on the selected processor, merchant account and customer location/device. No live payment method is connected by this guide. Employees will use company-provided wallet access; company administrators will manage payment through the website.

How does the employee pricing discount work?#

Planned pricing is $14.99 per active employee per month for 1–10 employees, and $12.99 for every active employee once the company has 11–50. Thus 10 employees total $149.90 and 11 total $142.89 per month before applicable tax. Above 50 requires an annual enterprise agreement. The 30-day trial, final employee-count measurement and renewal terms will be disclosed during commercial signup.

Is an AI setup assistant available?#

Ask COTG is planned for the administrator workspace. It will answer setup and usage questions using approved help and provide source links. Its first release will give read-only guidance; changes to employees, approvals, access and billing remain actions for authorized people. Until it is released, use this guide and the resource center.

Where will Contact us messages go?#

The planned website form will route sales, support and billing inquiries to monitored COTG mailboxes. Final addresses and delivery are still being configured; use the designated pilot support contact until a working destination is published. Do not send passwords, full card details or employee certificates through a public inquiry form.

Is the 41-class list legally required for every employee?#

No. The 41 CCI names are an optional starter list. Each Customer approves its own catalog, applicability, employee selections, evidence rules and expiration policies.

Can I remove a default requirement from one employee?#

A clerk or administrator can uncheck a baseline requirement on the employee profile and choose Save baseline requirements. A requirement still needed by an active site assignment remains effective until that assignment is deliberately closed. The change is audited and evidence/history is retained. Follow the company's approval policy; this checklist does not provide a separate waiver workflow.

Does an approved record mean the employee is legally compliant?#

It means an authorized company reviewer approved the submitted evidence under company policy. Laws, regulator rules, customer contracts, and site rules may require more.

Who can change employee records?#

Authorized office users according to their role. Employees use a read-only wallet in the current release.

Can an employee upload a certificate from the phone app?#

Not in the current release. The office workflow maintains and approves evidence.

Does an auditor need an account or the COTG app?#

No. The employee presents a QR code and the auditor opens a limited browser view.

How long does an auditor link work?#

The normal production duration is displayed when the link is created and is currently 15 minutes. It may be revoked sooner.

Can a production QR code be non-expiring?#

No. Non-expiring links are restricted to allowlisted fictional pre-alpha demonstrations. Production defaults to no permanent shares.

Can someone reuse a screenshot of the QR code?#

They may be able to use it while the link remains active. That is why the employee should display it only when needed and why the production link is short-lived and revocable.

Does the QR prove identity?#

It displays the Customer's published profile and photo. It does not replace a government ID or guarantee that the person presenting the code is the employee. The auditor applies the site's identity-check process.

Does Face ID send a face scan to COTG?#

Under the intended design, no. The device performs the biometric comparison and returns a success/failure result. Any architecture change requires privacy and legal review before release.

Can an employee use a password instead of biometrics?#

Yes, using the supported sign-in flow, unless the Customer imposes another lawful policy.

Does the wallet work offline?#

No. The current release requires internet access to retrieve current records and create or open auditor links.

What happens if a credential expires while a renewal is pending?#

The earlier approved credential remains the active version until it expires or is revoked. Pending evidence does not become approved automatically.

Can I edit an old approved certificate?#

Use renewal/versioning so the history remains intact. Do not overwrite reviewed source evidence to make it look different.

Why is the dashboard percentage blank?#

A company with no assigned requirements displays no percentage. This avoids implying 100% readiness when nothing has been measured.

Why does the dashboard not include an inactive employee?#

Dashboard calculations count active employees. Historical records remain subject to company retention policy.

Does changing a role delete old requirements?#

No. A profile or role change leaves the saved requirement list unchanged. Edit the requirement checklist explicitly when assignments need to change; earlier proof remains in history.

Can CSV import update existing employees?#

No. The current import creates new employees only. Edit an existing profile through the application.

What happens if one row in the import is bad?#

The preview identifies errors for correction. A validated batch is committed transactionally so it does not intentionally create a partial roster if the commit fails.

Are upload files public?#

No. Photos and certificate files are stored on private paths and delivered after authorization. QR sharing exposes only the approved auditor view for the active link.

Are uploads scanned for viruses?#

Not in the current release. Upload known business records from trusted sources. Malware scanning is a broad-launch requirement.

Are automated expiration emails active?#

No. The dashboard shows the warning window, but automated notification delivery is not enabled.

Can I connect Paycom or Samsara now?#

No. The current integration area is planning-only and must not contain credentials. Live connectors require separate implementation and source-of-truth decisions.

Are office invitations emailed automatically?#

No. Administrators create accounts and deliver credentials through the approved secure process.

Is self-service password recovery available?#

No. Use the administrator/support reset process.

Is multi-factor authentication available?#

Not in the current release. It remains a broad-launch security item.

Who fixes an incorrect employee record?#

The Customer administrator controls Customer records. Employees should use the company's published correction process.

Can the system replace every physical certificate?#

Only after the Customer confirms that each applicable regulator, client, facility, contract, and policy accepts the digital presentation. Keep required physical proof until then.

What should I do if data appears under the wrong company?#

Stop work, avoid further downloads, preserve the minimum evidence needed, and contact the pilot incident team immediately.

What should I do before a company-wide rollout?#

Complete every production-pilot exit gate in docs/website/PRODUCTION_PILOT.md, including legal approval, physical-device testing, backup restoration, access review, data reconciliation, and incident-response readiness.

Support escalation template#

Provide the following without including passwords or unnecessary certificate content:

• company name;
• your name and office role;
• date, time, and time zone;
• employee number or record ID, if relevant;
• screen and action attempted;
• expected and actual result;
• device, operating system, app/browser version;
• whether the issue affects one user or multiple users;
• screenshot with unrelated personal data removed; and
• urgency and operational deadline.

Pilot support email: support@credentialsonthego.com
Pilot support phone: No public support telephone is listed; use the support email.
Security/incident contact: support@credentialsonthego.com — request incident escalation.