Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement - Expand Documentation Regarding Graph API Permissions #678

Open
1 task done
robertcaretta opened this issue Jul 25, 2023 · 2 comments
Open
1 task done

Comments

@robertcaretta
Copy link

robertcaretta commented Jul 25, 2023

Category

  • Feature request

Is your feature request related to a problem?

No.

Describe the solution you'd like

Could you please expand the documentation to specify which webparts use which exact Graph API permissions. It is not clear to me on the main webpart summary page, or on the respective individual webpart documentation and code pages. If this information was in the documentation it would more readily accessible to stakeholders for evaluation prior to deployment.

Describe alternatives you've considered

  • Deployed to a developer tenant.
  • Read through the existing available documentation.

Additional context

When deploying an older version of starter kit to the app catalog there is also not enough detail in regards to which webpart is using which graph api permissions.
image

The newer version does provide the information at deployment time.
image

@ghost
Copy link

ghost commented Jul 25, 2023

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

@ghost ghost added the Needs: Triage 🔍 label Jul 25, 2023
@robertcaretta
Copy link
Author

robertcaretta commented Jul 25, 2023

I was also able to find what I was looking for by making the column "Web Api Permissions Scopes Requested" visible in the app catalog. However, this information is available post deployment.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant