-commit_email_docs_link=s_('Profiles|This email will be used for web based operations, such as edits and merges. %{commit_email_link_start}Learn more%{commit_email_link_end}').html_safe%{commit_email_link_start: commit_email_link_start,commit_email_link_end: '</a>'.html_safe}
-commit_email_docs_link=s_('Profiles|This email will be used for web based operations, such as edits and merges. %{commit_email_link_start}Learn more%{commit_email_link_end}').html_safe%{commit_email_link_start: commit_email_link_start,commit_email_link_end: '</a>'.html_safe}
| [User account](user/profile/index.md) | Manage your account. |
| [User account](user/profile/index.md) | Manage your account. |
| [Authentication](topics/authentication/index.md) | Account security with two-factor authentication, set up your SSH keys, and deploy keys for secure access to your projects. |
| [Authentication](topics/authentication/index.md) | Account security with two-factor authentication, set up your SSH keys, and deploy keys for secure access to your projects. |
| [User settings](user/profile/index.md#user-settings) | Manage your user settings, two factor authentication, and more. |
| [User settings](user/profile/index.md#access-your-user-settings) | Manage your user settings, two factor authentication, and more. |
| [User permissions](user/permissions.md) | Learn what each role in a project can do. |
| [User permissions](user/permissions.md) | Learn what each role in a project can do. |
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22560) in GitLab 11.5.
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22560) in GitLab 11.5.
This configuration option sets the email hostname for [private commit emails](../../profile/index.md#private-commit-email).
This configuration option sets the email hostname for [private commit emails](../../profile/index.md#use-an-automatically-generated-private-commit-email).
By default it is set to `users.noreply.YOUR_CONFIGURED_HOSTNAME`.
By default it is set to `users.noreply.YOUR_CONFIGURED_HOSTNAME`.
see [this procedure in the GitLab Team Handbook](https://about.gitlab.com/handbook/tools-and-tips/#how-to-change-your-username-at-gitlabcom).
before proceeding.
To change your `username`:
To change your username:
1. Navigate to your [user settings](#user-settings).
1. In the top-right corner, select your avatar.
1. Select **Edit profile**.
1. In the left sidebar, select **Account**.
1. In the left sidebar, select **Account**.
1.Enter a new username under **Change username**.
1.In the **Change username** section, enter a new username as the path.
1. Select **Update username**.
1. Select **Update username**.
WARNING:
## Make your user profile page private
It is not possible to change your username if it contains a
project with [Container Registry](../packages/container_registry/index.md) tags,
because the project cannot be moved.
NOTE:
If you want to retain ownership over the original namespace and
protect the URL redirects, then instead of changing a group's path or renaming a
username, you can create a new group and transfer projects to it.
Alternatively, you can follow [this detailed procedure from the GitLab Team Handbook](https://about.gitlab.com/handbook/tools-and-tips/#how-to-change-your-username-at-gitlabcom)
which also covers the case where you have projects hosted with
[GitLab Pages](../project/pages/index.md).
## Private profile
The following information is hidden from the user profile page (`https://gitlab.example.com/username`) if this feature is enabled:
You can make your user profile visible to only you and GitLab administrators.
- Atom feed
- Date when account is created
- Activity tab
- Groups tab
- Contributed projects tab
- Personal projects tab
- Starred projects tab
- Snippets tab
To make your profile private:
To make your profile private:
...
@@ -142,11 +70,13 @@ To make your profile private:
...
@@ -142,11 +70,13 @@ To make your profile private:
1. Select the **Private profile** checkbox.
1. Select the **Private profile** checkbox.
1. Select **Update profile settings**.
1. Select **Update profile settings**.
NOTE:
The following is hidden from your user profile page (`https://gitlab.example.com/username`):
All your profile information can be seen by yourself and GitLab administrators even if
the **Private profile** option is enabled.
- Atom feed
- Date when account was created
- Tabs for activity, groups, contributed projects, personal projects, starred projects, snippets
## Add details of external accounts
## Add external accounts to your user profile page
You can add links to certain other external accounts you might have, like Skype and Twitter.
You can add links to certain other external accounts you might have, like Skype and Twitter.
They can help other users connect with you on other platforms.
They can help other users connect with you on other platforms.
...
@@ -155,58 +85,47 @@ To add links to other accounts:
...
@@ -155,58 +85,47 @@ To add links to other accounts:
1. In the top-right corner, select your avatar.
1. In the top-right corner, select your avatar.
1. Select **Edit profile**.
1. Select **Edit profile**.
1.Edit the desired fields for external accounts:
1.In the **Main settings** section, add your information from:
- Skype
- Skype
- LinkedIn
- LinkedIn
- Twitter
- Twitter
1. Select **Update profile settings**.
1. Select **Update profile settings**.
## Private contributions
## Show private contributions on your user profile page
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/14078) in GitLab 11.3.
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/14078) in GitLab 11.3.
Enabling private contributions includes contributions to private projects, in the user contribution calendar graph and user recent activity.
In the user contribution calendar graph and recent activity list, you can show contributions to private projects.
To enable private contributions:
To show private contributions:
1. In the top-right corner, select your avatar.
1. In the top-right corner, select your avatar.
1. Select **Edit profile**.
1. Select **Edit profile**.
1.Select the **Private contributions** checkbox.
1.In the **Main settings** section, select the **Include private contributions on my profile** checkbox.
1. Select **Update profile settings**.
1. Select **Update profile settings**.
## Current status
## Set your current status
> Introduced in GitLab 11.2.
> Introduced in GitLab 11.2.
You can provide a custom status message for your user profile along with an emoji that describes it.
You can provide a custom status message for your user profile along with an emoji that describes it.
This may be helpful when you are out of office or otherwise not available.
This may be helpful when you are out of office or otherwise not available.
Other users can then take your status into consideration when responding to your issues or assigning work to you.
Please be aware that your status is publicly visible even if your [profile is private](#private-profile).
Status messages are restricted to 100 characters of plain text.
Your status is publicly visible even if your [profile is private](#make-your-user-profile-page-private).
They may however contain emoji codes such as `I'm on vacation :palm_tree:`.
To set your current status:
To set your current status:
1. In the top-right corner, select your avatar.
1. In the top-right corner, select your avatar.
1. Select **Set status**, or **Edit status** if you have already set a status.
1. Select **Set status** or, if you have already set a status, **Edit status**.
1. Set the desired emoji and status message.
1. Set the desired emoji and status message. Status messages must be plain text and 100 characters or less.
They can also contain emoji codes like, `I'm on vacation :palm_tree:`.
1. Select **Set status**. Alternatively, you can select **Remove status** to remove your user status entirely.
1. Select **Set status**. Alternatively, you can select **Remove status** to remove your user status entirely.
or
You can also set your current status by [using the API](../../api/users.md#user-status).
1. In the top-right corner, select your avatar.
1. Select your name or username.
1. Select the Edit profile icon (**{pencil}**).
1. Enter your status message in the **Your status** text field.
1. Select Add status emoji icon (**{slight-smile}**), and select the desired emoji.
1. Select **Update profile settings**.
You can also set your current status [using the API](../../api/users.md#user-status).
If you previously selected the **Busy** checkbox, remember to deselect it when you become available again.
If you select the **Busy** checkbox, remember to clear it when you become available again.
## Busy status indicator
## Set a busy status indicator
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/259649) in GitLab 13.6.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/259649) in GitLab 13.6.
> - It was [deployed behind a feature flag](../feature_flags.md), disabled by default.
> - It was [deployed behind a feature flag](../feature_flags.md), disabled by default.
...
@@ -217,23 +136,19 @@ If you previously selected the **Busy** checkbox, remember to deselect it when y
...
@@ -217,23 +136,19 @@ If you previously selected the **Busy** checkbox, remember to deselect it when y
To indicate to others that you are busy, you can set an indicator.
To indicate to others that you are busy, you can set an indicator.
To set the busy status indicator, either:
To set the busy status indicator, either:
- Set it directly:
- Set it directly:
1. In the top-right corner, select your avatar.
1. In the top-right corner, select your avatar.
1. Select **Set status**, or **Edit status** if you have already set a status.
1. Select **Set status** or, if you have already set a status, **Edit status**.
1. Select the **Busy** checkbox.
1. Select the **Busy** checkbox.
- Set it on your profile:
- Set it on your profile:
1. In the top-right corner, select your avatar.
1. In the top-right corner, select your avatar.
1. Select **Edit profile**.
1. Select **Edit profile**.
1.Select the **Busy** checkbox.
1.In the **Current status** section, select the **Busy** checkbox.
Once selected, you can see the busy status in various locations in the user interface.
The busy status is displayed in the user interface.
Username:
Username:
...
@@ -270,7 +185,7 @@ To enable it:
...
@@ -270,7 +185,7 @@ To enable it:
Feature.enable(:set_user_availability_status)
Feature.enable(:set_user_availability_status)
```
```
## Commit email
## Change the email displayed on your commits
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/21598) in GitLab 11.4.
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/21598) in GitLab 11.4.
...
@@ -282,29 +197,27 @@ To change your commit email:
...
@@ -282,29 +197,27 @@ To change your commit email:
1. In the top-right corner, select your avatar.
1. In the top-right corner, select your avatar.
1. Select **Edit profile**.
1. Select **Edit profile**.
1. Select the **Commit email** dropdown.
1. In the **Commit email** list, select an email address.
1. Select any of the verified emails.
1. Select **Update profile settings**.
1. Select **Update profile settings**.
### Private commit email
### Use an automatically-generated private commit email
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22560) in GitLab 11.5.
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22560) in GitLab 11.5.
GitLab provides the user with an automatically generated private commit email option,
GitLab provides an automatically-generated private commit email address,
which allows the user to keep their email information private.
so you can keep your email information private.
To enable this option:
To use a private commit email:
1. In the top-right corner, select your avatar.
1. In the top-right corner, select your avatar.
1. Select **Edit profile**.
1. Select **Edit profile**.
1. Select the **Commit email** dropdown.
1. In the **Commit email** list, select the **Use a private email** option.
1. Select **Use a private email** option.
1. Select **Update profile settings**.
1. Select **Update profile settings**.
After this option is enabled, every Git-related action is performed using the private commit email.
Every Git-related action uses the private commit email.
To stay fully anonymous, you can also copy this private commit email
To stay fully anonymous, you can also copy the private commit email
and configure it on your local machine using the following command:
and configure it on your local machine by using the following command:
@@ -116,7 +116,7 @@ LDAP Users remain confirmed if all of the following conditions are met:
...
@@ -116,7 +116,7 @@ LDAP Users remain confirmed if all of the following conditions are met:
- The ["User email confirmation at sign-up" option](../security/user_email_confirmation.md) is set to false.
- The ["User email confirmation at sign-up" option](../security/user_email_confirmation.md) is set to false.
- The first sign-in is based on user LDAP credentials.
- The first sign-in is based on user LDAP credentials.
- The user has added and verified [a secondary email address](profile/index.md#user-settings) some time later.
- The user has added and verified [a secondary email address](profile/index.md) some time later.
NOTE:
NOTE:
Confirmation timestamps (primary vs. secondary) are different.
Confirmation timestamps (primary vs. secondary) are different.
...
@@ -124,6 +124,6 @@ Confirmation timestamps (primary vs. secondary) are different.
...
@@ -124,6 +124,6 @@ Confirmation timestamps (primary vs. secondary) are different.
Users remain unconfirmed by the background migration if any of the following conditions are met:
Users remain unconfirmed by the background migration if any of the following conditions are met:
- They [create an account through GitLab](profile/account/create_accounts.md).
- They [create an account through GitLab](profile/account/create_accounts.md).
- They [swap their primary email address](profile/index.md#user-settings) and verify it.
- They [swap their primary email address](profile/index.md#change-the-email-displayed-on-your-commits) and verify it.
- If they have two email addresses with the same `confirmed_at` timestamp due to the linked [security issue](https://gitlab.com/gitlab-org/gitlab/-/issues/121664).
- If they have two email addresses with the same `confirmed_at` timestamp due to the linked [security issue](https://gitlab.com/gitlab-org/gitlab/-/issues/121664).
-[LDAP is introduced](../administration/auth/ldap/index.md), and users' primary email address matches that in LDAP.
-[LDAP is introduced](../administration/auth/ldap/index.md), and users' primary email address matches that in LDAP.
