Testers move between clients every week, the schedule lives in a spreadsheet, and every client expects their evidence to stay theirs. Neuron gives the practice one operating picture without mixing anyone's data.
How a provider runs parallel engagements in one Neuron deployment, using features that ship in Neuron today.
The Gantt schedule shows every engagement, assessment, phase and retest across the practice. Filter by client or person, drag work between testers, and let the overload view catch double bookings.
Each recurring client has an engagement template holding its assessments, team, QA reviewers and access, so this month's engagement starts where last month's was set up.
Whoever is staffed writes from the same approved library and the same playbooks, so the fortieth report of the month reads like the first.
Findings flow into review queues with amber and red aging. Overdue items go out in a daily digest, so review keeps pace as headcount grows.
Each client sees only their own engagements in the Delivery Portal. Their engineers see only the engagements assigned to them.
Every sign-in, view and download is logged per client, with an all-clients view for the practice and a CSV export.
Timings are examples.
Engagements, assessments, phases and retests share one Gantt view, with allocations that cascade from an engagement down to its assessments and phases. Drop work on a tester to reassign it, and resolve conflicts in place.
Portal accounts belong to one client organization. Admin, Manager and Read only roles see that client's engagement history. The Engineer role sees only what you assign, for clients with contractors or large teams.
Findings stay invisible until you release them. Partial release shows the number, title, severity and status; full release adds the write-up.
An approved library variant per assessment type and language, briefs with a version per language, and playbooks with coverage built from step states. A tester's improvement only flows back to the library after it clears QA.
The Custom Branding module puts your practice's name and look on the Delivery Portal and its sign-in pages. Watermarks on delivered PDFs carry the recipient's identity and, if you choose, their IP address.
Neuron is one deployment you run. Clients are separated inside it by access and release controls, not by separate hosted tenants.
Neuron schedules and delivers the work. Contracts, invoicing and time sheets stay where they are.
Client records hold contacts, locations and portal access for the engagement. Sales pipelines belong elsewhere.
Each portal account belongs to one client organization and sees only that client's released work. Staff access is set per engagement team, and unreleased findings are invisible in the portal.
Yes. The Engineer portal role sees only the engagements explicitly assigned to it, unlike Admin, Manager and Read only, which see the client's whole history.
Yes. Portal sign-in supports OIDC and SAML per client, alongside MFA with backup codes for password accounts.
Yes. Each client has a portal activity log of sign-ins, views, downloads and status changes, exportable to CSV, and deliverables under Controlled Release carry a signed acknowledgement receipt.
No. Neuron runs on infrastructure you control, and we never receive your findings, evidence or credentials.
No. Neuron AI is a separate, optional module. When you use it, the models run on your hardware and no prompt is sent to a third-party provider.
We will walk you through scheduling, delivery and client separation in Neuron, on a deployment you would operate.