Granular Data Collection #46
paulmccrady
started this conversation in
Ideas
Replies: 2 comments
-
|
Thanks for your idea. As we discussed in the Q&A section I really like the idea of using decent controlled and documented permission sets. I have opened issue #47 and plan to start work on it soon. Related to this I have also opened #48 to improve export coverage without excessive permissions. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
v0.2.0 has just been released. In this release is a new feature to specify the level of access available for the PAT through a |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
At present the data collection part of the 'Export' functions call a number of APIs that the user has no control over. Some of these APIs require Full Access PAT permissions. Can we include a feature that allows the user/caller to choose whether to include data collection that requires tokens with such large/sensitive/destructive permissions sets ?
Beta Was this translation helpful? Give feedback.
All reactions