Raklet uses shared login sessions across the *.raklet.com domain. This means if you’re accessing both the member portal and admin panel under Raklet subdomains (e.g., testorganization.raklet.com and admin.raklet.com), your session carries over automatically. Once logged in, your session should be active for 30 days.
However, if your organization uses a custom domain (e.g., www.customdomainorg.com), your login session does not carry over to Raklet’s admin panel, because cookies set on your custom domain are not accessible on raklet.com. Raklet uses domain-specific cookies for login sessions. This means that even if you’re logged into one domain (like your custom member portal), your session isn’t automatically active on another domain (like Raklet’s admin panel).
Why does this happen?
Browsers isolate sessions between different domains for security reasons. So if you're logged in at your custom domain (like www.customdomainorg.com), that session is not valid for raklet.com — and vice versa.
What you should do?
Log in to your member portal (hosted on your custom domain):
https://www.customdomainorg.com/loginAlso, log in to the admin panel (hosted on Raklet):
https://login.raklet.com/?permalink=yourorganizationname
Once logged into both, you’ll stay signed in on each for up to 30 days unless you log out manually.
If you’re still seeing a different admin account or cannot access your organization:
Make sure you’re not logged in with another email address on admin.raklet.com.
If needed, log out completely from both portals and re-login with the correct credentials.
Example Case:
You’re logged in at www.customdomainorg.com and try to go to admin.raklet.com, but it either redirects or shows a different account. That’s because your login session on the custom domain isn’t recognized on raklet.com. You simply need to log in again