- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cannot access Manage My Team
If I go to Case Support->Manage my team, I get the error below that I don’t have an active agreement. MyRSA shows our active contract though. Should I be using a different method to add users to RSA Link for our organization? I don't think I've tried since the migration.
If I am on this page and select Manage My Team, I get “no records found”.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
i cannot access this either and cannot find another way to do so.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @LaurenBrodt and @JoeSutton,
I'm sorry for the inconvenience that this issue has been. We have engaged our IT team to investigate the issue and will let you know as soon as your issue has been resolved so that you can try again.
Thanks!
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm facing the same issue, it says access not permitted and the page is temporarily unavailable.
Am trying to put up a case where authentication is failing, saying that user attempted to authenticate using authenticator "SecurID_Native", but the user belongs to security domain "SystemDomain".
Appreciate any help urgently pls
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've the same issue "No Record found"
== Edit ==
4h later .. now it works again 🤔
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your update made me try again and now it works ¯\_(ツ)_/¯
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And now back to no record found...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Was there a resolution here? We are experiencing this same issue.
