#garymoon-dashboard-permissions
pearl cove
regal shadow
Apologies for the delay. Can pick up the conversation here. Are you looking to restrict this access in the API or dashboard? There are roles you can assign teammates in the dashboard and a couple tools if your people are using the API here
woven basin
The dashboard is our current concern. We're looking for something to prevent those who have access from making inadvertent or unilateral changes to production. Something like EC2 instance termination protection on AWS would do, or even better something like pull request reviews on Github where changes require approval from someone other than the author.
regal shadow
Have you looked in to roles here to see if they would help with your situation. They don't have fine-grained permissions but you could definitely use them to give users view only access to some data or not allow them to see some things at all https://stripe.com/docs/account/teams/roles
woven basin
There are only three people with access to production Stripe. We feel this strikes a good balance between availability of people with access (slash bus factor) and limiting access to as a few people as possible.
However, none of these people are inflaible, so we're looking for any way to limit the potential for accidental or otherwise unilateral changes to a production system.
mental sigil
there isn't really a way/solution for this. You can listen to Events on your webhook endpoint to catch changes but that's it. If someone has write access to the Dashboard they can make changes and some of those could be dangerous
woven basin
Okay thanks everyone 👍
mental sigil
garymoon-dashboard-permissions
woven basin
Perhaps instead of preventing changes, being notified would be enough. Is there any mechanism (other than writing our own via webhook) by which we might be notified via email or Slack etc of any prod changes?