Back to Nevada Unemployment

Esmeralda Gómez

Unemployment login employer issue - Nevada DETR account access problem

Okay so I'm completely lost and need help figuring this out. I was laid off from my job at a mid-sized logistics company about six weeks ago and went to file my unemployment claim through the Nevada DETR CSS portal. When I tried to log into my account on nui.nv.gov, something went seriously wrong - the system apparently pulled up information tied to my former employer's account instead of showing me a claimant view. Or at least that's what it looked like, because I was seeing wage records and business registration stuff that made zero sense for someone just trying to file a UI claim. I panicked and immediately logged out. Now every time I try to sign back in with my credentials, it either throws an error saying my account has restricted access or it loops me back to the login page without letting me through at all. I've never seen anything like this before. My previous unemployment claim years ago was totally straightforward. I'm worried this glitch might have flagged my account somehow or messed up my claim before it even got properly submitted. I've been without income for six weeks now and I still don't know if my claim is even in the system. Has anyone run into something like this where the CSS portal confused your claimant login with employer records? Is there a way to get this untangled without waiting forever?

What browser were you using when this happened? Genuinely asking because I had something similar where the CSS portal was showing me weird screens that didn't belong in a claimant account, and it turned out to be a browser caching issue making the site pull old session data. Chrome was the worst offender for me. Try completely clearing every cookie and cached file for nui.nv.gov specifically, then open a fresh private/incognito window and log in from scratch. Don't use any saved passwords - type your credentials manually. See if that changes what you're seeing.

0 coins

Tried that just now - cleared everything in Chrome, switched to Firefox actually, went incognito, typed everything manually. Still getting the access restricted error. It won't even let me get to that weird employer-looking screen anymore, just bounces me at the login page.

0 coins

Same error happened to my cousin and the browser thing didn't fix it either. She ended up having to create a whole new account with a different email and then call DETR to link her claim to the new login. Pain in the neck but it worked eventually.

0 coins

Worth trying the account recovery option on the CSS login page too - there's a specific recovery flow that's different from just resetting your password. The password reset sometimes makes the lockout worse if the account has a flag on it already.

0 coins

Sounds like your claimant account might have gotten cross-linked with employer credentials in the system, which is a known but rare CSS glitch. Have you ever been listed as an owner or officer of any Nevada business? Even something minor like being an authorized contact for a small business can sometimes cause the portal to give your SSN dual access roles, which then creates exactly the kind of conflict you're describing where you see employer-side information when you're trying to log in as a claimant.

0 coins

No business ownership at all, never registered anything in Nevada. Just a regular W-2 employee my whole working life. That's what makes this so confusing.

0 coins

Actually I'd ask DETR directly something like 'do I have more than one access role tied to my SSN in the CSS system' because if there's a dual-role conflict on the backend, nothing you do on your end will fix it - it has to be manually corrected by their tech team. That's the kind of thing that sits in a queue for weeks if nobody flags it properly.

0 coins

Exactly what I was going to say. The claimant portal and the employer portal share some backend infrastructure and when accounts get cross-tagged, it confuses the authentication layer. DETR's IT team can scrub the duplicate role but you have to get someone on the phone who knows to escalate it to the right department rather than just resetting your password.

0 coins

Getting DETR on the phone lately though - good luck with that the normal way. I had an account issue a few months back that required talking to an actual agent and I tried their main line probably a dozen times over two weeks before I got through. Eventually someone in a Facebook group mentioned Claimyr - it basically works the hold line for you so you end up talking to a live Nevada DETR agent without spending your whole day redialing. There's a demo video at https://youtu.be/Mc9FNfOF_yY and the site is claimyr.com. Honestly saved me from losing my mind. For something like a login/employer account mix-up you really do need a human agent, not just the automated system.

0 coins

How long did it take once you used it before you were actually talking to someone at DETR?

0 coins

Tried it after seeing it mentioned somewhere else - ended up speaking with a DETR rep the same day, which was more than I managed after two weeks of trying on my own.

0 coins

Does it work for the CSS technical issues specifically or only for claim status stuff? Asking because I have a different login problem I've been trying to sort out.

0 coins

Can I ask something that might sound basic - when you first created your CSS account, did you use your personal email or possibly an email that was also used by your employer for business purposes? Like a work email address? Because if the email tied to your claimant login is the same one your former employer registered with their Nevada UI employer account, the portal can get seriously confused about which account type to authenticate you into. Happened to someone I know who set up their unemployment account with their work email before they were officially terminated.

0 coins

Oh. Oh no. I did use my work email because I still had access to it when I first filed and it was easier to remember. That might actually be exactly what caused this.

0 coins

Yeah that's almost certainly it then. Your work email was probably the contact on file for your employer's UI account. When you registered as a claimant with the same address, the system flagged an authentication conflict. You need a DETR agent to manually separate the two accounts and migrate your claim to a personal email. This isn't something CSS self-service can fix.

0 coins

This is such a common trap and DETR really should warn people about it. I always tell anyone filing unemployment - use a personal Gmail or something completely unconnected to your employer before you even start the application.

0 coins

Two months into my own claim and I'm still seeing adjudication pending so just commiserating here, the Nevada DETR system is genuinely a mess. But on your specific issue - once you do get through to an agent, make sure you ask them to verify that your weekly claim certifications aren't being lost in the system while your login is broken. Some people get back access to their account and find out they have a gap in their weekly claims that caused issues with their payment timeline.

0 coins

That's a really good point I hadn't even thought about. I've been so focused on just getting into my account that I didn't consider whether the weekly certifications were building up unfiled behind the scenes.

0 coins

Ask the agent specifically to check your claim effective date and whether any certification weeks are showing as missed versus pending. They can sometimes backfill or note the reason for the gap if it was a system access issue rather than claimant error.

0 coins

Same thing happened to me with missed weeks - agent noted it as a technical access issue and it didn't penalize my claim. Document everything about when you tried to log in and when you got the errors just in case.

0 coins

Just want to mention that Claimyr came up in another thread I was reading about CSS account problems and multiple people there said it got them to an agent who could actually handle technical account issues, not just the tier-one reps who can only read you what's on the screen. Something about the specific routing getting to a higher-level support person. Worth trying if you've had no luck with the main DETR number. claimyr.com is where to go.

0 coins

Already got the info from an earlier comment - will definitely be using it today. Need to get this sorted before I miss another week of certifications.

0 coins

Second this for account-level technical problems. Regular DETR reps told me three times to just reset my password before someone actually looked at the backend of my account and found the real issue.

0 coins

Yeah the tier-one people are kind of limited in what they can actually see in the system. Getting to someone who has full account access makes a massive difference for anything beyond basic claim status questions.

0 coins

Stepping back to give you the full picture on what DETR will probably need to do here: they'll have to disassociate your email address from the employer account in their system, then verify your claimant profile is intact and not corrupted, then reset your login credentials tied to a new personal email address. The tricky part is making sure your existing claim data - your base period wages, your weekly benefit amount calculation, your effective date - all transfers correctly to the updated account. Ask the agent specifically to confirm your claim data is preserved after they make the account changes, don't just assume it carries over automatically.

0 coins

This is incredibly helpful, thank you. I'm going to write all of this down before I call so I know exactly what to ask for and confirm.

0 coins

Also ask them to send you a confirmation via your CSS message center once the account is corrected, so you have a record that the fix was made. If anything goes wrong later you'll want that documentation.

0 coins

Good point about the base period wages - I had an account issue that got fixed but my wage records from one quarter disappeared in the process and my WBA got recalculated lower. Had to call again to get it corrected. Always double-check your wage data after any account modification.

0 coins

The claim effective date protection is especially important. Some agents will just create a fresh account from scratch rather than properly migrating the existing claim data, and then your effective date gets reset to whenever they made the new account, costing you weeks of back pay.

0 coins

Wait, is this something that can happen to anyone or just people who made an account with a work email? Asking because I haven't filed yet and now I'm second-guessing my setup.

0 coins

Use a personal email, not tied to any employer, and you'll be fine. The conflict only happens when the same email address exists in both the employer registration side and the claimant registration side of the CSS system.

0 coins

Okay good, I've got a separate personal email I use for everything non-work. Sounds like I should be safe then. Thanks for the quick answer.

0 coins

Also make sure your username is unique to you and not something like your employee ID number from your old job. Some people set that as their username without thinking and it can cause different kinds of authentication headaches.

0 coins

DETR's CSS portal has had issues with employer/claimant account conflicts for YEARS and they still haven't fixed the underlying problem. You're not the first person to post about this and you definitely won't be the last. The fact that they let people register with any email address without checking if it's already in their employer database is just bad system design. Really frustrating that individual claimants have to deal with this.

0 coins

The worst part is that when you call about it, half the agents don't even know this glitch exists and try to tell you it's something you did wrong during registration.

0 coins

Exactly. I spent 45 minutes on hold once only to be told to clear my cookies and try again. Like... no. That is not the solution to a backend account conflict.

0 coins

They did update the CSS system somewhat in 2024 but apparently didn't address this particular issue. At least the weekly certification process got slightly less confusing.

0 coins

Something worth asking about when you get an agent: does the conflict affect your wage records visibility at all? The reason I bring this up is that your former employer submits quarterly wage reports to DETR, and if the system has them cross-linked to your claimant account in a weird way, it's theoretically possible your wage data could be in a weird state too. Probably fine, but worth confirming your base period wages are showing correctly once you have account access restored.

0 coins

I actually hadn't even considered whether the employer account conflict might mess with how my wages are reported. Good thing to verify. Adding it to my list of questions for the agent.

0 coins

It's probably just a login authentication layer issue that doesn't go deeper than account access, but since you're going to be talking to an agent anyway, takes two seconds to ask them to pull up your wage record and confirm the base period looks right.

0 coins

This happened to someone I know and the wage records were totally fine - the conflict was only at the authentication level, not in the claim data itself. But yes, confirming it doesn't hurt anything.

0 coins

just went through something adjacent to this, not the exact same situation but my employer had filed their quarterly wages late and my claim was stuck for three weeks because DETR couldn't verify my wages. totally different cause but same feeling of being locked out of your own claim with no information and no way to get anyone on the phone. it's awful. hope you get this resolved quickly.

0 coins

Ugh, three weeks for a wage verification issue - that sounds brutal. Did they backpay the weeks once it was sorted?

0 coins

Yes eventually got all the back weeks paid out but it took another week after the fix before the payments actually hit. So patience required even after they fix it.

0 coins

Late employer wage reporting is such an underrated source of claim delays. DETR should proactively notify claimants when that's the reason for a hold instead of making people figure it out themselves.

0 coins

Read through this whole thread because I had a totally different CSS login issue last month. Mine was just a standard lockout after too many wrong password attempts but I could not get through to DETR for three days. Someone mentioned Claimyr and I figured I had nothing to lose - ended up speaking to a Nevada DETR agent within a few hours and they unlocked my account while I was on the call. For anyone dealing with any kind of CSS technical problem, it's genuinely the most reliable way I found to reach a real person at DETR. claimyr.com and there's a video at https://youtu.be/Mc9FNfOF_yY showing what to expect.

0 coins

My lockout was different from what you described - mine was a two-factor verification issue - but I had the same experience of just not being able to reach anyone for days.

0 coins

The hold times on DETR's regular line have been ridiculous lately. Even calling right when they open you can easily wait an hour or more and sometimes get disconnected before anyone picks up.

0 coins

Tried calling at 8am on a Tuesday thinking I'd beat the rush - got through the phone tree and then sat on hold for 90 minutes before the call dropped. Never want to do that again.

0 coins

Quick tip that might help while you're waiting to get the account issue fixed: screenshot or write down every error message you see on the CSS portal with the date and time. If your claim ends up with a gap in weekly certifications because you couldn't access your account, having that documentation of when the technical issue started makes it much easier for DETR to process an exception and not penalize you for the missed weeks.

0 coins

Already started doing this after someone else mentioned documentation. Have screenshots going back to when the issue first started six days ago.

0 coins

Good. Also screenshot your claim status page whenever you can access it, even partial views. Any evidence that the system was misbehaving on DETR's end, not yours, helps your case.

0 coins

Can't stress this enough - documentation saved my claim when I had a gap in certifications due to a system issue. Without the screenshots I would have had a much harder time explaining what happened.

0 coins

Also keep any emails you got from DETR during this period, like any automated messages about your account status. Those timestamps help establish the timeline of when the access issue started.

0 coins

Something nobody's mentioned yet - once you get this fixed, make sure you go into your CSS account settings and set up two different contact methods, your personal email and a phone number, so if there's ever another authentication issue DETR has a secondary way to reach you. The system is supposed to be able to send account recovery to either one, and having both set up adds a layer of protection against getting locked out again.

0 coins

Good preventive tip. Once this nightmare is resolved I will absolutely be making sure the account is set up properly going forward.

0 coins

Also update your preferred contact to your personal email in the CSS profile settings as soon as you have access - that takes about 30 seconds and closes the loop on the original issue.

0 coins

Setting up the phone number for account recovery is underrated. Email recovery sometimes has delivery delays with DETR's system and the SMS verification is way faster when you need to get back in urgently.

0 coins

Random but slightly related - does anyone know if the employer can see when you file for unemployment against them? My situation is different from OP but I've been nervous to file because my layoff was kind of contentious and I don't want my former boss to get any notification that I'm collecting.

0 coins

Ask DETR 'what notices go to my former employer when I file' - because yes, employers do receive a formal notice that a UI claim has been filed that may affect their account. They get the opportunity to respond with their side of the separation, which is normal procedure. But them receiving that notice doesn't affect your ability to collect if you meet the eligibility requirements - most standard layoffs sail through without any issue.

0 coins

Okay so they will find out but it doesn't necessarily cause problems for a regular layoff - that's reassuring actually. I was worried they could somehow block my claim just out of spite.

0 coins

They can contest the claim and give their version of the separation but for a true layoff it usually doesn't go anywhere. If they claim you were fired for misconduct instead of laid off, that's when it can get complicated and you might need to go through adjudication.

0 coins

OP please update us when this gets resolved? I have a friend in a similar situation who I'm going to point to this thread and knowing how it turned out would help her know what to expect.

0 coins

Will do. Trying Claimyr today to get through to DETR since the normal line hasn't worked for me. I'll post back once I know what's happening.

0 coins

Fingers crossed for you. Six weeks without income is a long time to be dealing with a technical glitch.

0 coins

Seriously hoping this gets resolved quickly. The CSS technical issues seem to be more common lately and it would be good to have a documented resolution path in this thread for others who run into the same thing.

0 coins

One more thing to flag - when you're talking to the DETR agent about the employer/claimant account conflict, ask them to note in your claim file that the reason for any delay or gap in certifications was a system-side technical access issue rather than a claimant error or failure to certify. Having that notation in your file protects you if anyone reviews your claim down the line and sees the gap. Some agents will add it without being asked but not all of them.

0 coins

Noted - asking for a file notation is going on my list right now. This thread has honestly given me a whole checklist to work through.

0 coins

Good luck. For what it's worth, most of these CSS account conflicts do get resolved once you have the right agent looking at the backend. It's just getting to that person that's the battle.

0 coins

The file notation thing is genuinely important - had a reviewer flag a gap in my certifications months after the fact and it turned into a whole thing that could have been avoided if the original agent had just added the note at the time.

0 coins

Circling back to the phone access question since it keeps coming up in this thread - I know Claimyr was mentioned a couple times already but just adding that it worked specifically for a CSS technical issue I had (not just claim status or payment stuff). The agent I spoke with had access to the full account backend and was able to see the error flag on my account that the tier-one people couldn't even find. So it's not just for simple questions, it got me to someone with actual system access. Worth trying if you're still having trouble getting through.

0 coins

Good to know it works for the technical side too. I assumed it was mainly useful for payment questions.

0 coins

Nope, any reason you'd need to talk to DETR. The key is you're getting to a live agent who can actually look at your account, and some of them have deeper system access than others.

0 coins

The difference between a tier-one rep who just reads the screen and someone with actual backend access is huge. Glad there's a way to increase the odds of getting the second kind.

0 coins

For what it's worth, I work adjacent to HR in my industry and have seen the employer side of unemployment claims. The employer CSS portal and the claimant CSS portal are genuinely different interfaces on the same underlying system, which is exactly why a shared email can create an authentication nightmare. Employers log in to report wages, respond to claims, and manage their UI tax rate. When the system sees one email trying to authenticate into both roles simultaneously, it doesn't know which interface to serve and sometimes just throws access errors rather than picking one. It's a design flaw that DETR knows about.

0 coins

This is a really clear explanation of what's actually happening mechanically. Makes total sense why a shared email causes the conflict.

0 coins

Yeah it's one of those legacy system issues where the two portals were probably built at different times and bolted together without fully accounting for credential overlap. Fixing it properly would require a significant system rebuild.

0 coins

Which explains why it's still a problem years later. DETR isn't going to do a full system rebuild anytime soon.

0 coins

At least now there's a workaround - getting an agent to manually separate the accounts and migrate the claim data. Not elegant but it works.

0 coins

Nevada Unemployment AI

Expert Assistant
Secure