How can we help?

PoPayOne signs you in with a password-free email link. If it hasn't arrived after a minute or two, check your spam/junk folder and any company mail quarantine — the sender is Supabase Auth on our behalf.

Still nothing? On the sign-in page, choose “Use a different email” and send a fresh link (or re-enter the same address — each send issues a new link).

Links are single-use and expire quickly. If you open an expired or already-used link, the sign-in page shows a banner and your details are saved — just request a fresh link from there and you'll land back where you left off.

After you submit a business document, your workspace shows “Under review” while the PoPay team checks it. Our review target is 2 business days.

Your workspace stays fully usable in the meantime — you can add clients, consultants, placements and timesheets while the review runs. If we need one more document, the home screen shows exactly what's missing and you can resubmit from Settings.

The worker portal invite is claimed by email: the consultant signs in with the email address saved on their record, and the portal links to their profile automatically. Any personal email works — it doesn't need to be a company address.

Known limitation: a consultant added without an email can't self-serve into the portal. The fix is simple — the workspace owner/admin edits the consultant's record to add an email, and the invite becomes claimable with that address.

The conversational setup accepts typed answers everywhere — if the microphone is blocked or transcription hiccups, just type into the same box and continue.

If the conversation itself gets stuck, use the classic form-based setup instead: sign in and finish with the classic setup. Nothing is created until you confirm the review card, so switching paths never leaves a half-built workspace.

Workspace owners & admins see their own business's workspace — relationships, people, placements, timesheets, funding, compliance — scoped by the role they hold. Every action is capability-gated, and businesses are never co-mingled: row-level security isolates each business's data at the database.

Workers (consultants) see only their own world: their profile, their work-authorization documents (and who each is shared with), their projects — active and history — and their own timesheets. Nothing company-internal leaks into the worker portal; approving hours stays an employer action.

Insurance agencies see only the COI requests addressed to them, with the requirements and holder wording, and can upload and manage certificates back into the requesting workspace. They see nothing else about the business.

Immigration firms are separate cross-business tenants: firm users see every case assigned to their firm across all the businesses that engaged it — each row mapped to its business and consultant — plus documents shared on those cases, and only that.

Immigration providers (external experts) see just the individual cases assigned to them and the case documents shared with them — a narrower window than a firm, scoped case by case.

No. PoPayOne is in an early-access pilot: funding features run on simulated funds over mock bank and insurer rails — no real money moves, and the funding marketplace is early access / waitlist.

The controls are real, though: every money action needs a single-use, resource-bound confirmation and a capability check, large disbursements need a second approver, and everything posts to a double-entry, hash-chained audit ledger. An MFA step-up on money actions is enforced in real-money mode.