2 ms·
It's on Azure, so maybe it uses the same permissions nightmare as Teams.
by robertlagrant 5y ago
It's on Azure, so maybe it uses the same permissions nightmare as Teams.
- yeldarb 5y agoNah this is my my bad. Revamping the API Key permission logic to be aware that the person who created the project might not be the same person accessing it via API now that we have public sharing was a known “todo” that I deprioritized until users started running into it! Prioritizing now that there’s actually some traffic discovering it.
- robertlagrant 5y agoI'm sure - I was just ragging on Teams :) Deprioritised TODOs are the best!