Edits to user Profile and Settings content
Each of these files were edited to ensure compliance with the docs standard layout, as part of the SSOT epic. In addition, some copy editing was done, to improve clarity, and comply with the GitLab docs style guide.
This commit is contained in:
Russell Dickenson
Evan Read
parent
13c2b7698d
commit
783b05959a
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
type: howto
|
||||
---
|
||||
|
||||
# Deleting a User account
|
||||
|
||||
Users can be deleted from a GitLab instance, either by:
|
||||
|
|
@ -64,8 +68,20 @@ for such records. Any commits made by a deleted user will still display the
|
|||
username of the original user.
|
||||
|
||||
When a user is deleted from an [abuse report](../../admin_area/abuse_reports.md)
|
||||
or spam log, these associated records are not ghosted and will be removed, along
|
||||
with any groups the user is a sole owner of.
|
||||
or spam log, these associated
|
||||
records are not ghosted and will be removed, along with any groups the user
|
||||
is a sole owner of. Administrators can also request this behavior when
|
||||
deleting users from the [API](../../../api/users.md#user-deletion) or the
|
||||
Admin Area.
|
||||
|
||||
Administrators can also request this behavior when deleting users from the
|
||||
[API](../../../api/users.md#user-deletion) or the Admin Area.
|
||||
<!-- ## Troubleshooting
|
||||
|
||||
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
|
||||
one might have when setting this up, or when something is changed, or on upgrading, it's
|
||||
important to describe those, too. Think of things that may go wrong and include them here.
|
||||
This is important to minimize requests for support, and to avoid doc comments with
|
||||
questions that you know someone might ask.
|
||||
|
||||
Each scenario can be a third-level heading, e.g. `### Getting error message X`.
|
||||
If you have none to add when creating a doc, leave this section in place
|
||||
but commented out to help encourage others to add to it in the future. -->
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
type: howto
|
||||
---
|
||||
|
||||
# Two-Factor Authentication
|
||||
|
||||
Two-factor Authentication (2FA) provides an additional level of security to your
|
||||
|
|
@ -15,7 +19,7 @@ When you enable 2FA, don't forget to back up your [recovery codes](#recovery-cod
|
|||
|
||||
In addition to time-based one time passwords (TOTP), GitLab supports U2F
|
||||
(universal 2nd factor) devices as the second factor of authentication. Once
|
||||
enabled, in addition to supplying your username and password to login, you'll
|
||||
enabled, in addition to supplying your username and password to log in, you'll
|
||||
be prompted to activate your U2F device (usually by pressing a button on it),
|
||||
and it will perform secure authentication on your behalf.
|
||||
|
||||
|
|
@ -238,3 +242,15 @@ Sign in and re-enable two-factor authentication as soon as possible.
|
|||
- The user logs out and attempts to log in via `first.host.xyz` - U2F authentication succeeds.
|
||||
- The user logs out and attempts to log in via `second.host.xyz` - U2F authentication fails, because
|
||||
the U2F key has only been registered on `first.host.xyz`.
|
||||
|
||||
<!-- ## Troubleshooting
|
||||
|
||||
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
|
||||
one might have when setting this up, or when something is changed, or on upgrading, it's
|
||||
important to describe those, too. Think of things that may go wrong and include them here.
|
||||
This is important to minimize requests for support, and to avoid doc comments with
|
||||
questions that you know someone might ask.
|
||||
|
||||
Each scenario can be a third-level heading, e.g. `### Getting error message X`.
|
||||
If you have none to add when creating a doc, leave this section in place
|
||||
but commented out to help encourage others to add to it in the future. -->
|
||||
|
|
|
|||
|
|
@ -1,14 +1,31 @@
|
|||
---
|
||||
type: howto
|
||||
---
|
||||
|
||||
# Active Sessions
|
||||
|
||||
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/17867)
|
||||
> in GitLab 10.8.
|
||||
|
||||
GitLab lists all devices that have logged into your account. This allows you to
|
||||
review the sessions.
|
||||
review the sessions, and revoke any you don't recognize.
|
||||
|
||||
## Listing all active sessions
|
||||
|
||||
1. On the upper right corner, click on your avatar and go to your **Settings**.
|
||||
1. Navigate to the **Active Sessions** tab.
|
||||
1. Click your avatar.
|
||||
1. Select **Settings**.
|
||||
1. Click **Active Sessions** in the sidebar.
|
||||
|
||||
|
||||
|
||||
<!-- ## Troubleshooting
|
||||
|
||||
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
|
||||
one might have when setting this up, or when something is changed, or on upgrading, it's
|
||||
important to describe those, too. Think of things that may go wrong and include them here.
|
||||
This is important to minimize requests for support, and to avoid doc comments with
|
||||
questions that you know someone might ask.
|
||||
|
||||
Each scenario can be a third-level heading, e.g. `### Getting error message X`.
|
||||
If you have none to add when creating a doc, leave this section in place
|
||||
but commented out to help encourage others to add to it in the future. -->
|
||||
|
|
|
|||
|
|
@ -1,7 +1,12 @@
|
|||
---
|
||||
type: index, howto
|
||||
---
|
||||
|
||||
# User account
|
||||
|
||||
When signed into their GitLab account, users can customize their
|
||||
experience according to the best approach to their cases.
|
||||
Each GitLab account has a user profile, and settings. Your [profile](#user-profile)
|
||||
contains information about you, and your GitLab activity. Your [settings](#profile-settings)
|
||||
allow you to customize some aspects of GitLab to suit yourself.
|
||||
|
||||
## Signing in
|
||||
|
||||
|
|
@ -10,8 +15,10 @@ See the [authentication topic](../../topics/authentication/index.md) for more de
|
|||
|
||||
## User profile
|
||||
|
||||
Your profile is available from the up-right corner menu bar (user's avatar) > **Profile**,
|
||||
or from `https://example.gitlab.com/username`.
|
||||
To access your profile:
|
||||
|
||||
1. Click on your avatar.
|
||||
1. Select **Profile**.
|
||||
|
||||
On your profile page, you will see the following information:
|
||||
|
||||
|
|
@ -24,8 +31,10 @@ On your profile page, you will see the following information:
|
|||
|
||||
## Profile settings
|
||||
|
||||
You can edit your account settings by navigating from the up-right corner menu bar
|
||||
(user's avatar) > **Settings**, or visiting `https://example.gitlab.com/profile`.
|
||||
To access your profile settings:
|
||||
|
||||
1. Click on your avatar.
|
||||
1. Select **Settings**.
|
||||
|
||||
From there, you can:
|
||||
|
||||
|
|
@ -56,8 +65,8 @@ before proceeding.
|
|||
To change your `username`:
|
||||
|
||||
1. Navigate to your [profile's](#profile-settings) **Settings > Account**.
|
||||
1. Enter a new username under "Change username".
|
||||
1. Hit **Update username**.
|
||||
1. Enter a new username under **Change username**.
|
||||
1. Click **Update username**.
|
||||
|
||||
CAUTION: **Caution:**
|
||||
It is currently not possible to change your username if it contains a
|
||||
|
|
@ -86,12 +95,15 @@ The following information will be hidden from the user profile page (`https://gi
|
|||
|
||||
To enable private profile:
|
||||
|
||||
1. Navigate to your personal [profile settings](#profile-settings).
|
||||
1. Check the "Private profile" option.
|
||||
1. Hit **Update profile settings**.
|
||||
1. Click your avatar.
|
||||
1. Select **Profile**.
|
||||
1. Click **Edit profile** (pencil icon).
|
||||
1. Check the **Private profile** option in the **Main settings** section.
|
||||
1. Click **Update profile settings**.
|
||||
|
||||
NOTE: **Note:**
|
||||
You and GitLab admins can see your the abovementioned information on your profile even if it is private.
|
||||
All your profile information can be seen by yourself, and GitLab admins, even if
|
||||
the **Private profile** option is enabled.
|
||||
|
||||
## Add details of external accounts
|
||||
|
||||
|
|
@ -99,9 +111,15 @@ GitLab allows you to add links to certain other external accounts you might have
|
|||
|
||||
To add links to other accounts:
|
||||
|
||||
1. Navigate to your **User Settings > Profile**.
|
||||
1. In the **Main settings** section, locate and fill out fields for links to external accounts like Skype and Twitter.
|
||||
1. Click the **Update profile settings** button.
|
||||
1. Click your avatar.
|
||||
1. Select **Profile**.
|
||||
1. Click **Edit profile** (pencil icon).
|
||||
1. Complete the desired fields for external accounts, in the **Main settings**
|
||||
section:
|
||||
- Skype
|
||||
- Twitter
|
||||
- LinkedIn
|
||||
1. Click **Update profile settings**.
|
||||
|
||||
## Private contributions
|
||||
|
||||
|
|
@ -111,9 +129,11 @@ Enabling private contributions will include contributions to private projects, i
|
|||
|
||||
To enable private contributions:
|
||||
|
||||
1. Navigate to your personal [profile settings](#profile-settings).
|
||||
1. Check the "Private contributions" option.
|
||||
1. Hit **Update profile settings**.
|
||||
1. Click on your avatar.
|
||||
1. Select **Profile**.
|
||||
1. Click **Edit profile** (pencil icon).
|
||||
1. Check the **Private contributions** option.
|
||||
1. Click **Update profile settings**.
|
||||
|
||||
## Current status
|
||||
|
||||
|
|
@ -124,22 +144,24 @@ 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.
|
||||
They may however contain emoji codes such as `I'm on vacation :palm_tree:`.
|
||||
|
||||
To set your current status:
|
||||
|
||||
1. Open the user menu in the top-right corner of the navigation bar.
|
||||
1. Hit **Set status**, or **Edit status** if you have already set a status.
|
||||
1. Set the emoji and/or status message to your liking.
|
||||
1. Hit **Set status**. Alternatively, you can also hit **Remove status** to remove your user status entirely.
|
||||
1. Click your avatar.
|
||||
1. Click **Set status**, or **Edit status** if you have already set a status.
|
||||
1. Set the desired emoji and/or status message.
|
||||
1. Click **Set status**. Alternatively, you can click **Remove status** to remove your user status entirely.
|
||||
|
||||
or
|
||||
|
||||
1. Navigate to your personal [profile settings](#profile-settings).
|
||||
1. In the text field below `Your status`, enter your status message.
|
||||
1. Select an emoji from the dropdown if you like.
|
||||
1. Hit **Update profile settings**.
|
||||
|
||||
Status messages are restricted to 100 characters of plain text.
|
||||
They may however contain emoji codes such as `I'm on vacation :palm_tree:`.
|
||||
1. Click your avatar.
|
||||
1. Select **Profile**.
|
||||
1. Click **Edit profile** (pencil icon).
|
||||
1. Enter your status message in the **Your status** text field.
|
||||
1. Click **Add status emoji** (smiley face), and select the desired emoji.
|
||||
1. Click **Update profile settings**.
|
||||
|
||||
You can also set your current status [using the API](../../api/users.md#user-status).
|
||||
|
||||
|
|
@ -153,34 +175,36 @@ Any of your own verified email addresses can be used as the commit email.
|
|||
|
||||
To change your commit email:
|
||||
|
||||
1. Click on your avatar at the top-right corner of the navigation bar.
|
||||
1. From the menu that appears, click **Settings**.
|
||||
1. In the **Main settings** section, locate **Commit email** dropdown.
|
||||
1. Click your avatar.
|
||||
1. Select **Profile**.
|
||||
1. Click **Edit profile** (pencil icon).
|
||||
1. Click **Commit email** dropdown.
|
||||
1. Select any of the verified emails.
|
||||
1. Press **Update profile settings**.
|
||||
1. Click **Update profile settings**.
|
||||
|
||||
### Private commit email
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22560) in GitLab 11.5.
|
||||
|
||||
GitLab provides users with an automatically generated private commit email option,
|
||||
which allows the user to not make their email information public.
|
||||
GitLab provides the user with an automatically generated private commit email option,
|
||||
which allows the user to keep their email information private.
|
||||
|
||||
To enable this option:
|
||||
|
||||
1. Click on your avatar at the top-right corner of the navigation bar.
|
||||
1. From the menu that appears, click **Settings**.
|
||||
1. In the **Main settings** section, locate **Commit email** dropdown.
|
||||
1. Select the "Use a private email" option.
|
||||
1. Press **Update profile settings**.
|
||||
1. Click your avatar.
|
||||
1. Select **Profile**.
|
||||
1. Click **Edit profile** (pencil icon).
|
||||
1. Click **Commit email** dropdown.
|
||||
1. Select **Use a private email** option.
|
||||
1. Click **Update profile settings**.
|
||||
|
||||
Once this option is enabled, every Git-related action will be performed using the private commit email.
|
||||
|
||||
In order to stay fully anonymous, you can also copy this private commit email
|
||||
To stay fully anonymous, you can also copy this private commit email
|
||||
and configure it on your local machine using the following command:
|
||||
|
||||
```sh
|
||||
git config --global user.email <YOUR_PRIVATE_COMMIT_EMAIL>
|
||||
git config --global user.email <your email address>
|
||||
```
|
||||
|
||||
## Troubleshooting
|
||||
|
|
@ -203,3 +227,15 @@ to get you a new `_gitlab_session` and keep you signed in through browser restar
|
|||
|
||||
After your `remember_user_token` expires and your `_gitlab_session` is cleared/expired,
|
||||
you will be asked to sign in again to verify your identity (which is for security reasons).
|
||||
|
||||
<!-- ## Troubleshooting
|
||||
|
||||
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
|
||||
one might have when setting this up, or when something is changed, or on upgrading, it's
|
||||
important to describe those, too. Think of things that may go wrong and include them here.
|
||||
This is important to minimize requests for support, and to avoid doc comments with
|
||||
questions that you know someone might ask.
|
||||
|
||||
Each scenario can be a third-level heading, e.g. `### Getting error message X`.
|
||||
If you have none to add when creating a doc, leave this section in place
|
||||
but commented out to help encourage others to add to it in the future. -->
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
type: concepts, howto
|
||||
---
|
||||
|
||||
# Personal access tokens
|
||||
|
||||
> [Introduced][ce-3749] in GitLab 8.8.
|
||||
|
|
@ -52,3 +56,15 @@ the following table.
|
|||
[container registry]: ../project/container_registry.md
|
||||
[users]: ../../api/users.md
|
||||
[usage]: ../../api/README.md#personal-access-tokens
|
||||
|
||||
<!-- ## Troubleshooting
|
||||
|
||||
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
|
||||
one might have when setting this up, or when something is changed, or on upgrading, it's
|
||||
important to describe those, too. Think of things that may go wrong and include them here.
|
||||
This is important to minimize requests for support, and to avoid doc comments with
|
||||
questions that you know someone might ask.
|
||||
|
||||
Each scenario can be a third-level heading, e.g. `### Getting error message X`.
|
||||
If you have none to add when creating a doc, leave this section in place
|
||||
but commented out to help encourage others to add to it in the future. -->
|
||||
|
|
|
|||
|
|
@ -1,11 +1,17 @@
|
|||
---
|
||||
type: concepts, howto
|
||||
---
|
||||
|
||||
# Profile preferences
|
||||
|
||||
A user's profile preferences page allows the user to customize various aspects
|
||||
of GitLab to their liking.
|
||||
|
||||
To navigate to your profile's preferences, click your avatar icon in the top
|
||||
right corner, select **Settings** and then choose **Preferences** from the
|
||||
left sidebar.
|
||||
To navigate to your profile's preferences:
|
||||
|
||||
1. Click your avatar.
|
||||
1. Select **Settings**.
|
||||
1. Click **Preferences** in the sidebar.
|
||||
|
||||
## Navigation theme
|
||||
|
||||
|
|
@ -15,7 +21,7 @@ and left side navigation.
|
|||
Using individual color themes might help you differentiate between your different
|
||||
GitLab instances.
|
||||
|
||||
The default palette is Indigo. You can choose between 10 different themes:
|
||||
The default theme is Indigo. You can choose between 10 themes:
|
||||
|
||||
- Indigo
|
||||
- Light Indigo
|
||||
|
|
@ -39,7 +45,7 @@ for syntax highlighting. For a list of supported languages visit the rouge websi
|
|||
Changing this setting allows you to customize the color theme when viewing any
|
||||
syntax highlighted code on GitLab.
|
||||
|
||||
The default syntax theme is White, and you can choose among 5 different colors:
|
||||
The default syntax theme is White, and you can choose among 5 different themes:
|
||||
|
||||
- White
|
||||
- Dark
|
||||
|
|
@ -102,7 +108,7 @@ Select your preferred language from a list of supported languages.
|
|||
|
||||
### First day of the week
|
||||
|
||||
The first day of the week can be customised for calendar views and date pickers.
|
||||
The first day of the week can be customized for calendar views and date pickers.
|
||||
|
||||
You can choose one of the following options as the first day of the week:
|
||||
|
||||
|
|
@ -111,3 +117,15 @@ You can choose one of the following options as the first day of the week:
|
|||
- Monday
|
||||
|
||||
If you select **System Default**, the system-wide default setting will be used.
|
||||
|
||||
<!-- ## Troubleshooting
|
||||
|
||||
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
|
||||
one might have when setting this up, or when something is changed, or on upgrading, it's
|
||||
important to describe those, too. Think of things that may go wrong and include them here.
|
||||
This is important to minimize requests for support, and to avoid doc comments with
|
||||
questions that you know someone might ask.
|
||||
|
||||
Each scenario can be a third-level heading, e.g. `### Getting error message X`.
|
||||
If you have none to add when creating a doc, leave this section in place
|
||||
but commented out to help encourage others to add to it in the future. -->
|
||||
|
|
|
|||
Loading…
Reference in New Issue