pnp / pnp/cli-microsoft365

Minimal permissions for 'spo sitedesign related' commands

Open
#7,505 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

docs help wanted
Dominant language
TypeScript
Stars
1.5k
Forks
413
Avg merge
5d 6h
Merged PRs (30d)
21

Description

We're adding a new Permissions section to all commands. This section will document the minimal delegated and application permissions required to execute the command.

The goal is to:

  • Make it easier to run the CLI with custom app registrations and application permissions.
  • Ensure we only document the minimal set of permissions needed.
  • Keep documentation consistent by placing the Permissions section right before the Examples section.
  • If there are multiple resources, order them alphabetically
  • If there are commands that only support one type of auth (like delegated or app-only), we have an example for that as well. E.g. m365 planner tenant settings list - Permissions
Resources
Commands in scope

This issue covers the following commands:

  • m365 spo sitedesign rights grant
  • m365 spo sitedesign rights list
  • m365 spo sitedesign rights revoke
  • m365 spo sitedesign run list
  • m365 spo sitedesign run-status get
  • m365 spo sitedesign task get
  • m365 spo sitedesign task list
  • m365 spo sitedesign task remove

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Writing the docs page and minimal-permissions guide, then locate the documentation pages for the eight listed spo sitedesign commands. Add a Permissions section before Examples on each page, documenting only the minimal delegated and application permissions and ordering multiple resources alphabetically; compare the linked Planner examples for the expected format.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
74/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.