You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/accounts/accounts/account-maintenance/account-email-settings.mdx
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,9 +42,20 @@ New Relic user email addresses have to the following restrictions:
42
42
<Calloutvariant="tip">
43
43
SSO/SAML users:
44
44
45
-
You can't update your email address while authenticated into a SSO/SAML account. You'll only be able to change your email address while logged into a non-SAML account.
45
+
You can update your email address while authenticated into a SSO/SAML account using one of these methods:
46
46
47
-
Your email address is used to authenticate you into New Relic. Until your identity provider is updated to match your new email address, you won't be able to log in to New Relic.
47
+
**Option 1: User Management UI**
48
+
1. Navigate to [user management](https://one.newrelic.com/admin-portal/organizations/users-list)
49
+
2. Click into your user details.
50
+
3. Update your email and save.
51
+
4. Update your email in your identity provider to match exactly.
52
+
5. Test authentication.
53
+
54
+
If you get logged out during this process and you're an admin, you can use the [one-time SSO bypass](/docs/accounts/accounts-billing/account-setup/troubleshoot-new-relics-password-email-address-login-problems/#login-troubleshooting) to regain access.
55
+
56
+
**Option 2: NerdGraph API**
57
+
58
+
You can update your email via the [NerdGraph API](/docs/apis/nerdgraph/examples/nerdgraph-manage-users/#update-users) to avoid any risk of being logged out. For bulk updates, see this [KCS article on bulk user email updates](https://knowledge.newrelic.com/s/article/Bulk-User-Email-Updates).
Copy file name to clipboardExpand all lines: src/content/docs/errors-inbox/browser-tab.mdx
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,3 +168,11 @@ For some older browsers, the following errors may be unavailable:
168
168
* Errors thrown from third-party scripts that reside on another domain are not available.
169
169
* Errors occurring on older browsers: These may not be able to provide a usable stack trace. In some cases, they may not provide a stack trace at all.
170
170
Error collection is done by wrapping JavaScript functions, so errors thrown by the browser at a lower level (such as [cross-origin resource sharing](http://en.wikipedia.org/wiki/Cross-origin_resource_sharing) errors) also are not available.
New Relic captures the `securitypolicyviolation` event emitted by browsers and reports any such occurrences. However, this begins in agent version 1.313.0 and is not yet integrated into the UI such as the Errors Inbox view.
175
+
Therefore, this data is only available through NRQL at this time. See the [attribute dictionary event](/attribute-dictionary/?event=SecurityPolicyViolation) for a list of reported attributes.
0 commit comments