This app is in beta: it’s live and ready to use, and some of its services are still being completed. Below is every claim on its Home and where it stands — and if something doesn’t work the way its Home says, tell the developers below.
verify — portal · 1.4.336 3105e76
What the Home says, checked against the app — 8 backed · 10 partly · 1 not yet · 1 not verified
Partly liveFirst-time customers set up access by receiving a code at the email or phone on file and then choosing their own password.Why: A phone number is only used to find the contact; the code always goes to the email on file, and the file itself says no SMS provider is configured.
Backed by the appCustomers sign in to the portal with their email and password.
Partly liveOn AppSite Pro, client portal access is billed at $1 a month per client active that month, with no charge for inactive clients.Why: Per-active-client monthly billing exists, but 'active' is written only for podcast guests who took part, and the $1 price comes from plan data, not code.
Backed by the appCustomers can review estimates and accept them before work starts.
Partly liveCustomers can see every invoice, paid or due, and view or download it.Why: Invoices are listed and can be paid, but there is no view or download of the invoice document.
Partly liveCustomers message the team in one thread per request.Why: Persisted threaded messaging exists, but conversations are generic tenant-wide channels and DMs. Nothing ties a thread to a customer request or creates one per request, and nothing separates a customer from the team.
Partly liveCustomers see their requests and items, each with its status and history.Why: Request data with status is fetched, but no page shown displays it with its history.
Partly liveCustomers see tasks being done for them and tasks waiting on them.Why: Tasks are shown and editable, but there is no split between work done for the customer and work waiting on them.
Partly livePodcast guests and talent see a 'My shows' list of the shows they are part of, with their segments and part, drawn from the host's production.Why: The UI exists, but the listing of segments and parts comes from the host's production through a function that is not shown.
Partly liveThe Profile page lets users manage their details, preferences and who can sign in.Why: Details are editable, but there are no preferences and no control over who can sign in.
Backed by the appStaff get a self-service profile with their own picture/avatar and password.
Backed by the appStaff see assigned courses in progress and earned badges read from the real training record.
Backed by the appA Stakeholders register records board, officers and advisors: who serves, in what capacity, from when, and who no longer does.
Backed by the appCustomers read the same records the team works in — one record on both sides, not a copy.
Partly liveThe module uses the same tenant identity, permissions, shared records, automation events and reporting conventions as the rest of AppSite.Why: Shared identity, tenancy and records are shown; automation events and reporting conventions are not shown for this module.
Partly liveCustomer Portal is included with every AppSite workspace, whatever the industry.Why: Portal is reachable on any plan only by fallback tier, nothing ties it to every workspace or industry, and onboarding does not add it automatically.
Backed by the appStaff can open the Portal in a Desk pane alongside a second module.
Backed by the appA Cyber Check badge reports live feature count, build and check date, and lets visitors report an issue.
Not checked yetA Customer Portal course is included free and opens in Training.Why: Content, not code: whether a specific free course exists cannot be settled by code.
On the wayVisitors can pick an industry to see the modules recommended for it.Why: No industry picker was shown.
The open tickets on this module’s own repository — what is being worked on right now.
The page and its back end, as the public reaches it.
✓Served over HTTPS
✓Every link and picture on the live Home answers
✓The live page loads without failed requests
✓No script errors on the live page
✓No insecure (http://) resources
✓Domain records (DNS)
✓Every link on the public page answers
✓Module info agrees (registry, catalogue, build)
✓No secret in the page or the JavaScript it ships
✕Deployed from main (the release branch) — being fixedserves dev-paul — releases ship from main (Developer module branch policy / the repo’s default branch)
Checked Oct 3, 2026, 6:20 p.m. against build 1.4.336 (3105e76). Cyber Check reads the Home a visitor sees, then compares every claim on it with the code of the build that is serving it — a label or a screenshot is not evidence; working code is. It also checks every link, HTTPS, shipped secrets, DNS, the public page, and the registry — then the other way: what the app offers that its Home never says. After a full first pass, it rechecks each app on any night its code, its build or its Home changed.