Skip to main content

Common Pitfalls When Using the User Management Dashboard (and How to Avoid Them)

The User Management Dashboard gives plan managers everything they need to manage accounts and support their teams. But like any powerful tool, there are a few common mistakes that can cause confusion or extra work.

The good news? Once you know what to watch out for, these pitfalls are easy to avoid. Here’s a list of the most frequent challenges districts run into — along with quick solutions and resources to help you navigate them.

1. Not Assigning a Plan Manager Role

What happens: Districts launch with licenses but never assign a plan manager.

Why it’s a problem: Without a plan manager, districts can’t access the dashboard to send invites to new staff and manage their users.

What to do instead: Assign at least one plan manager right away. Email help@slptoolkit.com to assign your plan managers.


2. Accessing the Dashboard Before Accepting the Plan Manager Invitation

What happens: A new plan manager tries to log into the dashboard before accepting their invitation.

Why it’s a problem: The dashboard appears black — not because of a bug, but because the invite hasn’t been accepted yet.

What to do instead: Accept the plan manager invitation first. Then, log in to access the dashboard.

👉Email help@slptoolkit.com if you need a new plan manager invitation.


3. Getting Stuck Behind Firewalls

What happens: Plan managers see a blank or a loading screen when opening the dashboard.

Why it’s a problem: This isn’t a system bug — it’s usually local IT blocking the dashboard site.

What to do instead: Have IT whitelist required domains and allow WebSockets.


4. Logging into the Wrong Site (slptoolkit.com instead of the Dashboard)

What happens: Plan managers try to log in at slptoolkit.com instead of the User Management Dashboard.

Why it’s a problem: They’re prompted to pay for a personal subscription, even though they’re trying to manage licenses — leading them to believe something is broken.

What to do instead: Plan managers should only log in athttps://user_management_9.jetadmin.io/login. Bookmark it! That’s the correct link for managing licenses, sending invites, and accessing reports.


5. Letting Invitations Expire

What happens: Invites expire after 7 days, leaving users unable to join.

Why it’s a problem: Plan managers sometimes think the system failed when their team is prompted to pay for a personal subscription to set up an account, but there actually isn’t an active invitation.

What to do instead: Resend the invite directly from the dashboard.


6. Over-Inviting Beyond Your License Count

What happens: More users are invited than licenses purchased.

Why it’s a problem: Only the first to accept gets in — the rest are blocked and prompted to purchase a subscription.

What to do instead: Double-check your license count before sending invites, transfer the account to the replacing staff member, free up licenses by deleting or disconnecting unneeded accounts, or request additional licenses from sales@slptoolkit.com.


7. Accidentally Deleting Accounts

What happens: Accounts are deleted without first checking with the staff member.

Why it’s a problem: Deletion permanently erases all student data, and the staff member loses access when they may still need it.

What to do instead: Double-check with the account holder first before deleting an account.


8. Assuming Student Data Transfers Automatically

What happens: A staff member leaves and the district assumes caseloads automatically move.

Why it’s a problem: Student data stays tied to the original account unless a transfer is completed.

What to do instead: Use the dashboard to transfer the account to the new staff member.


9. Trying to Transfer an Account to a User Who Already Has an Account

What happens: Plan managers attempt to transfer an account to a district email that’s already connected to another active account.

Why it’s a problem: Accounts cannot be merged, so the process fails. The system shows an error message — not because of a glitch, but because the email address is already taken.

What to do instead: Use a different district email that isn’t tied to another account, or transfer only the students to the existing account.


10. Adding an Extra Space After an Email Address

What happens: Plan managers transfer an account but accidentally add a trailing space after the email.

Why it’s a problem: The invite doesn’t send, and some plan managers try to “fix” it by deleting the account and sending a new invite. That creates bigger issues because the deleted account has to be restored.

What to do instead: Double-check for extra spaces when typing in the email field before clicking Update. When in doubt, always reach out to help@slptoolkit.com.


11. Mixing Up “Transfer Students” vs. “Transfer Accounts”

What happens: Some plan managers try to merge accounts, which isn’t possible in SLP Toolkit.

Why it’s a problem: This leads to confusion about where student data lives.

What to do instead:

  • Transfer Students if a provider is only picking up part of a caseload. This has to happen within the SLP Toolkit account.

  • Transfer the Entire Account if a new SLP is taking over the whole caseload and doesn’t already have an existing account. Plan managers can do this via the User Management Dashboard.
    👉 How to Transfer Students or Transfer Accounts


12. Forgetting About 2FA When Accessing Former Staff Accounts

What happens: Plan managers try to log into a former staff account but get stuck on Two-Factor Authentication (2FA).

Why it’s a problem: Without the code, they can’t access student records.

What to do instead: Disable 2FA in the dashboard and set a temporary password.


✅ With these pitfalls in mind — and the resources linked here — you’ll be ready to manage accounts smoothly, avoid common roadblocks, and keep your district running without interruption.

💡 Remember: you don’t have to figure this out alone. Our team is always happy to walk you through the steps. Email help@slptoolkit.com for assistance with using the User Management Dashboard.

Did this answer your question?