Trainual not working? Common problems, and the real fix

Login, permission, sync and notification issues

Trainual, a platform for writing up and assigning company process documentation with training-path tracking, is maintained software, and like any cloud platform, the practical problems that come up tend to fall into a few recurring categories rather than being genuinely unique each time.

• Login and session issues: someone can't access their account, or gets logged out unexpectedly. Check whether your account uses SSO through Okta or Microsoft Entra, since an SSO configuration issue on your end, not Trainual's, is a common cause here.
• Permission and role-assignment problems: content assigned to a role doesn't appear for someone who should have it, often because their role in Trainual's org chart doesn't match the role the training path was actually assigned to. This is usually a setup mismatch rather than a platform bug.
• Sync delays with connected systems: if you're using one of Trainual's HR or payroll integrations (Rippling, Paylocity, Workday and others), a new hire not appearing promptly is often a sync timing issue between the two systems rather than a failure in either one.
• Notifications not arriving: an assigned training path should typically trigger a notification, and if it doesn't, check the recipient's own notification settings and spam filtering before assuming the platform failed to send it.

I haven't independently verified Trainual's exact current troubleshooting steps for each of these from a live support article, since deeper help-center pages weren't accessible when checking for this guide. Trainual's own help center at help.trainual.com is the right place to confirm exact current steps for your specific issue.

When to contact support versus troubleshoot yourself

Check your own setup first for anything involving permissions, role assignment or notification settings, since these are commonly a configuration issue rather than a platform fault, and support will likely ask you to check them anyway before escalating. Contact support directly for anything that looks like a genuine outage (the platform is unreachable for everyone on your team, not just one person) or a billing or account-access issue, since those aren't things you can fix from your own settings.

A note on browser and device-specific issues, before assuming it's the platform

If a problem shows up for one person but not others, it's also worth ruling out their specific browser or device before assuming it's a Trainual account issue at all. An outdated browser version, a conflicting browser extension, or a mobile app that hasn't been updated recently are common, simple causes of display or functionality glitches that have nothing to do with Trainual's own account configuration. A quick test, trying the same action in a different browser or on a different device, isolates whether the problem travels with the person's specific setup or is genuinely tied to their Trainual account, which tells you immediately whether this is a local fix or something to escalate.

Prevent adoption problems, the real issue behind most "it's not working" complaints

In practice, the most common version of "Trainual isn't working" isn't a technical bug at all, it's staff not actually using what's been set up. This shows up as low completion rates, staff asking a colleague instead of checking their assigned training, or content that was written once and never updated as the real process changed. None of this is a support ticket, it's an adoption problem, and it has a different fix: make the training genuinely easy to find and complete (short, focused topics beat long ones), tell staff plainly that it's expected to be used and that flagging outdated content is welcome, and actually check the completion dashboard periodically rather than assuming it's being used just because it was set up correctly. A realistic first week is laid out in setting up Trainual for a 15 person team.

If you're seeing low adoption specifically because staff find switching to a separate app annoying mid-task, that's a real, structural limitation of any standalone training platform, not something a settings change fixes. That's the specific gap a tool embedded directly into systems staff already use daily, rather than a separate training app, is built to close. I weigh that choice in Trainual vs building your own training portal.

A simple diagnostic checklist before contacting support

Work through these in order before opening a support ticket, since they resolve a large share of reported issues without needing to wait on a response. First, confirm whether the issue affects one person or everyone, a single-person issue points toward their own account, permissions or notification settings; an everyone issue points toward a genuine platform problem worth escalating. Second, for a permissions issue specifically, check the person's assigned role in the org chart against the role the content was actually assigned to, a mismatch here is the single most common cause of "they should see this but don't." Third, for anything involving a connected HR or payroll system, check whether the sync has a known delay window, since a brand-new hire not appearing within minutes isn't necessarily a failure, it may just be the normal sync interval for that specific integration.

A worked example: diagnosing a specific reported problem

Say a manager reports that "training isn't working" for a new hire who can't see their assigned content. Walking the checklist: is it just this one person, yes, which points away from a platform outage. Check their role assignment in the org chart against the training path's assigned role, and find they were accidentally set up as "Office Coordinator" instead of "Customer Service Rep" during onboarding, a simple data-entry mismatch, not a bug. Correcting the role assignment resolves it immediately. This is a realistic example of how most "not working" reports actually resolve, a specific, checkable setup issue rather than a genuine platform fault, which is exactly why working through the checklist above before contacting support saves real time on both sides.

What to include if you do escalate to support

If your troubleshooting rules out a configuration issue and you do need to contact support, include specifics that speed up resolution: the exact error message or behavior, whether it affects one person or everyone, what you've already checked (role assignment, notification settings, a different browser), and roughly when the issue started. A ticket that says "it's broken" with no detail takes longer to resolve than one that already rules out the common causes, since support will otherwise need to ask you the same diagnostic questions this guide just walked through before they can actually investigate the real issue. If you're still deciding whether the platform suits you at all, my Trainual review covers fit and cost.

How I'd approach this

For a genuine technical issue, check your own setup first for permissions and notifications, since that resolves a large share of "not working" reports without needing support at all, then contact Trainual's support directly for anything that looks like a real platform fault. For the more common underlying problem, low adoption, the fix isn't technical: make training short and genuinely useful, set the expectation clearly with staff, and check the dashboard regularly rather than assuming correct setup equals actual use.