2020-06-23 00:09:42 +05:30
---
stage: Manage
2022-04-04 11:22:00 +05:30
group: Authentication and Authorization
2021-02-22 17:27:13 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-06-23 00:09:42 +05:30
---
2022-01-26 12:08:38 +05:30
# Email notification for unknown sign-ins **(FREE)**
2020-05-24 23:13:21 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/27211) in GitLab 13.0.
2021-02-22 17:27:13 +05:30
NOTE:
2020-07-28 23:09:34 +05:30
This feature is enabled by default for self-managed instances. Administrators may disable this feature
through the [Sign-in restrictions ](../admin_area/settings/sign_in_restrictions.md#email-notification-for-unknown-sign-ins ) section of the UI.
The feature is always enabled on GitLab.com.
When a user successfully signs in from a previously unknown IP address or device,
2020-05-24 23:13:21 +05:30
GitLab notifies the user by email. In this way, GitLab proactively alerts users of potentially
malicious or unauthorized sign-ins.
2020-07-28 23:09:34 +05:30
There are several methods used to identify a known sign-in. All methods must fail
for a notification email to be sent.
2020-05-24 23:13:21 +05:30
- Last sign-in IP: The current sign-in IP address is checked against the last sign-in
IP address.
- Current active sessions: If the user has an existing active session from the
same IP address. See [Active Sessions ](active_sessions.md ).
2020-07-28 23:09:34 +05:30
- Cookie: After successful sign in, an encrypted cookie is stored in the browser.
This cookie is set to expire 14 days after the last successful sign in.
2020-05-24 23:13:21 +05:30
## Example email
2021-09-04 01:27:46 +05:30
