Clarify artifacts:public effect on reporter role

What does this MR do?

When customer set the artifacts:public to false it will also hide the job/pipeline artifacts from users with the reporter role.

Updating this hopes to clarify this in the documentation.

Related issues

Ticket: https://gitlab.zendesk.com/agent/tickets/492886

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• 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 you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• 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 like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure 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.

added docsimprovement documentation maintenancerefactor typemaintenance labels

assigned to @cmarais

added Support Team Contributions label

marked the checklist item Follow the: as completed

added grouppipeline authoring label

added Category:Pipeline Composition devopsverify sectionci labels

	1 Warning
	8b6d7bfe: 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/ci/yaml/index.md (Link to current live version)
• doc/user/permissions.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

requested review from @lyspin

added docs-only label

added 1 commit

• 8b6d7bfe - Update permissions.md

Compare with previous version

changed milestone to %16.9

added Technical Writing label

resolved all threads

resolved all threads

resolved all threads

added 1 commit

• 4bdf138a - Minor style edits and link fix

Compare with previous version

approved this merge request

@cmarais Thank you for this MR! I went ahead and applied a few minor suggestions, including a change to fix the lint error for the broken link.

Approved and set to merge

enabled an automatic merge when all merge checks for 4bdf138a pass

merged

mentioned in commit 1eeb5b78

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

@lyspin.

mentioned in issue gitlab-com/support/support-team-meta#5831 (closed)

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