Skip to content

Add note on scope for internal projects

Emily Chang requested to merge docs-internal-projects-api into master

What does this MR do?

Currently, project access tokens are able to access Internal projects if it is created by an internal user as stated in the warning message for Creating project token which can be easily missed when users are reading the docs. If we look at the Scopes for Project Access Token section, it does not mention anything about internal projects, which implies that the access token is only limited to whichever project it is created from. This may be setting the wrong expectation as users were confused that their project access token was able to access another project

curl --request GET --header "PRIVATE-TOKEN: <private-token>" "https://gitlab.example.com/api/v4/projects"

Related issues

This issue came up in this internal ticket

Author's checklist

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.

Merge request reports