Add details about project feature settings

What does this MR do?

Adds a sentence to doc/public_access/public_access.md.

Related issues

Author's checklist (required)

• Follow the Documentation Guidelines and Style Guide.
• If you have Developer permissions or higher:
  • Ensure that the product tier badge is added to doc's h1.
  • Apply the documentation label, plus:
    • The corresponding DevOps stage and group labels, if applicable.
    • development guidelines when changing docs under doc/development/*, CONTRIBUTING.md, or README.md.
    • development guidelines and Documentation guidelines when changing docs under development/documentation/*.
    • development guidelines and Description templates (.gitlab/*) when creating/updating issue and MR description templates.
  • Assign the designated Technical Writer.

Do not add the feature, frontend, backend, ~"bug", or database labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.

When applicable:

• Update the permissions table.
• Link docs to and from the higher-level index page, plus other related docs where helpful.
• Add the product tier badge accordingly.
• Add GitLab's version history note(s).
• Add/update the feature flag section.

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

• Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

• Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
  • Ensure docs metadata are present and up-to-date.
  • Ensure Technical Writing and documentation are added.
  • Add the corresponding docs:: scoped label.
  • If working on UI text, add the corresponding UI Text scoped label.
  • Add twdoing when starting work on the MR.
  • Add twfinished if Technical Writing team work on the MR is complete but it remains open.

For more information about labels, see Technical Writing workflows - Labels.

For suggestions that you are confident don't need to be reviewed, change them locally and push a commit directly to save others from unneeded reviews. For example:

• Clear typos, like this is a typpo.
• Minor issues, like single quotes instead of double quotes, Oxford commas, and periods.

For more information, see our documentation on Merging a merge request.

3. Maintainer

1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
2. Ensure a release milestone is set.
3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

added documentation label

	46 Warnings
	651b3b1e: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	ca70f411: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	449dc6c4: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	8a5a2e64: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	f1f48e9f: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	56047f01: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	4aa6c2df: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	acc6b3a1: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	ea482c15: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	53b18d2d: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	2c545ca8: The commit subject may not be longer than 72 characters. For more information, take a look at our Commit message guidelines.
	cb14ff98: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	50209097: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	6ba779c5: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	683391c5: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	643a99cb: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	aac00cca: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	78fed439: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	a1873ad2: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	a1873ad2: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	873ba667: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	90ba60f0: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	d95e99f4: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	774d22f8: The commit subject may not be longer than 72 characters. For more information, take a look at our Commit message guidelines.
	1c483f7f: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	5a70276c: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	10627a13: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	1ed56ba8: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	4d48ee01: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	2a77b038: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	9fb4d3ac: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	3b10581a: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	5661d8c4: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	acbb1cf5: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	6c8bab8f: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	337033aa: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	2401d8ea: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	236fdb96: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	742d9d3d: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	5446ed10: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	daf8d8f5: The commit subject may not be longer than 72 characters. For more information, take a look at our Commit message guidelines.
	703d8dd9: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines.
	81364b3c: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	984145ac: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	8d69f13b: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	97772ee6: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.

	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/public_access/public_access.md

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

marked the checklist item Follow the Documentation Guidelines and Style Guide. as completed

marked the checklist item Ensure that the product tier badge is added to doc's h1. as completed

marked the checklist item Apply the documentation label, plus: as completed

added Community contribution label

mentioned in issue gitlab-org/quality/triage-reports#2001 (closed)

added devopsmanage groupauthentication and authorization [DEPRECATED] labels

added sectiondev label

mentioned in issue gitlab-org/quality/triage-reports#2062 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2211 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2435 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2625 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2805 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2996 (closed)

mentioned in issue gitlab-org/quality/triage-reports#3162 (closed)

mentioned in issue gitlab-org/quality/triage-reports#3424 (closed)

mentioned in issue gitlab-org/quality/triage-reports#3594 (closed)

mentioned in issue gitlab-org/quality/triage-reports#3764 (closed)

added 24484 commits

• 24f3b29d...510b8752 - 24483 commits from branch master
• c69013e7 - Merge branch 'master' into 'bbodenmiller-master-patch-44659'

Compare with previous version

Hi @gl-docsteam, please review this documentation Merge Request.

Please also consider updating the CODEOWNERS file in the https://gitlab.com/gitlab-org/gitlab project.

added twtriaged label

assigned to @bbodenmiller

requested review from @aqualls

changed milestone to %14.2

added maintenancerefactor tw-weight3 twdoing labels and removed twtriaged label

added docsimprovement label

This page doesn't have an owner, so I'll pick up the work. I'll label it devopscreate plus one of my groups, so it'll show up on my tallies for the month.

added devopscreate groupcode review labels and removed devopsmanage groupauthentication and authorization [DEPRECATED] labels

changed the description

added 1 commit

• f6d129a4 - Rephrase to active voice

Compare with previous version

approved this merge request

This merge request is small; no reason to sit on it. I've applied a comment to shift the language to active voice; approving and setting MWPS. Thanks @bbodenmiller!

@aqualls, thanks for approving this merge request.

Please consider starting a new pipeline if:

• This is the first time the merge request is approved, or
• The merge request is ready to be merged, and there has not been a merge request pipeline in the last 2 hours.

For more info, refer to the guideline.

resolved all threads

enabled an automatic merge when the pipeline for 14743cb3 succeeds

added Technical Writing label

removed twdoing label

added twfinished label

merged

mentioned in commit 2d79a895

And merged.

added workflowstaging label

added workflowcanary label and removed workflowstaging label

resolved all threads

added workflowproduction label and removed workflowcanary label

mentioned in issue gitlab-org/quality/triage-reports#4009 (closed)

mentioned in issue gitlab-org/quality/triage-reports#4018 (closed)