Add documentation on enabling admin mode
What does this MR do?
Adds documentation on enabling admin mode.
Related issues
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Merge request reports
Activity
assigned to @jglassman1
added sectiondev label
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/user/admin_area/settings/sign_in_restrictions.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
- Resolved by Hannah Sutor
Questions for clarification:
- Is it just administrators who can enable admin mode?
- When enabling admin mode, are permissions different depending on the method you use?
- Is it just administrators who can activate admin mode?
- I've made an assumption with the placeholder in the API call. Is the instance URL?
- I've made an assumption for the content on what happens with admin mode is deactivated or disabled. I've put it as both. Is this correct?
mentioned in issue #331508 (closed)
changed milestone to %15.6
requested review from @dblessing and @eread
- Resolved by Evan Read
Thank you @dblessing for answering my questions, tagging you and @eread for review.
- Resolved by Jon Glassman
- Resolved by Evan Read
- Resolved by Jon Glassman
- Resolved by Jon Glassman
removed review request for @eread
requested review from @eread
@eread thanks for the suggestions, I've made changes based on them. PTAL when you have a chance.
- Resolved by Evan Read
- Resolved by Evan Read
removed review request for @dblessing
- Resolved by Evan Read
- Resolved by Evan Read
- Resolved by Evan Read
requested review from @rdickenson and removed review request for @eread
@eread @jglassman1 - I've reviewed, approved, and merged this MR.
mentioned in commit 4f239137
added workflowstaging-canary label and removed workflowready for review label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
mentioned in merge request gitlab-com/www-gitlab-com!115396 (merged)
added releasedpublished label and removed releasedcandidate label