Quick answer
Newer Bluebeam is subscription-based: you sign in with a Bluebeam ID and each user needs an assigned seat. If it says seats are exceeded, sign out of Revu on a device you're not using (a named user gets up to three). If sign-in fails outright, confirm your email and password, ask your Org Admin to check your seat, and make sure a firewall/proxy isn't blocking Bluebeam's sign-in servers.
WHY IT HAPPENS
It's a subscription, tied to a login.
Current Bluebeam is a named-user subscription. You log in with a Bluebeam ID, and your organisation's Org Admin assigns each person a seat. Access is granted to a person, not a machine — a named user can be signed in on up to three devices. That means the usual sign-in problems are: no seat assigned to you, too many devices signed in, an expired offline period, or a firewall/proxy stopping Revu from reaching Bluebeam's licensing servers. Work through the list below.
HOW TO FIX IT
Work through these in order.
- Check you're using the right Bluebeam IDSign in with the exact email your subscription is registered to — not a personal address. If you're not sure of the password, use the "forgot password" link to reset it, then try again.
- Sign out on a device you're not usingIf you see "the maximum number of seats has been exceeded", you may simply be signed in on too many machines. A named user gets three devices — sign out of Revu on your old laptop or a spare PC, then sign in on the one you need.
- Ask your Org Admin to confirm your seatEvery user needs a seat assigned to them in Bluebeam's subscription management (Org Admin). If you've never signed in, or a seat was reassigned, you may not have one. Your Org Admin (the licence owner or IT) can assign or free up a seat for you.
- Check whether all seats are genuinely in use"Seats exceeded" can also mean the whole plan is full — every seat allocated to other staff. The Org Admin can see who holds seats, reclaim ones from people who've left, or buy more so there's capacity.
- Reconnect if you've been offline too longA subscription seat works offline for a limited grace period, then Revu needs to reach the internet to re-check your entitlement. If it's demanding sign-in after a stretch offline, connect to the internet and sign in to refresh your licence.
- Clear the firewall / proxy path to BluebeamOn business networks, a firewall, web filter or proxy can block Bluebeam's sign-in and licensing servers, causing sign-in to fail or loop. If sign-in works on home/mobile data but not in the office, ask IT to allow Bluebeam through and disable proxy re-authentication for it.
- Restart Revu and try againFully close Revu (and the PC if needed) to clear a half-authenticated state, then reopen and sign in. Simple, but it clears a surprising number of stuck sign-ins after a password or seat change.
- Contact your admin or Bluebeam supportIf your seat is confirmed, you're within your device limit and the network is clear but sign-in still fails, it's an account-level issue. Your Org Admin should raise it with Bluebeam support with your Bluebeam ID and the exact error message.
If sign-in problems keep hitting the team — seats running out, people locked out after leaving, or the office network blocking activation — that's a licence-management and network job, not a per-person fix. Getting seat allocation, offboarding and firewall rules set up properly stops it recurring every time someone changes machines.
