pnp / pnp/cli-microsoft365

Minimal permissions for 'teams miscellaneous' commands

Open
#7,525 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 teams cache remove
  • m365 teams callrecord get
  • m365 teams callrecord list
  • m365 teams funsettings list
  • m365 teams funsettings set
  • m365 teams guestsettings list
  • m365 teams guestsettings set
  • m365 teams membersettings list
  • m365 teams membersettings set
  • m365 teams message reply list
  • m365 teams messagingsettings list
  • m365 teams messagingsettings set
  • m365 teams team app list
  • m365 teams user list

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 listed Teams command documentation pages and read the Writing the docs and minimal permissions guides. For each command, determine the minimal delegated and application permissions, order multiple resources alphabetically, and place a Permissions section immediately before Examples. Done means all 14 commands have consistent permission documentation, including auth-specific examples where applicable.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.