#therealbenji_best-practices
unborn ospreyBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1288610067255394315
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
wind bridge
Hi there
That does not sound ideal
Just to make sure I understand
when trying to set up a new developer account in Stripe's dashboard
Does this mean you were trying to add a new member here: https://dashboard.stripe.com/settings/team ?
wind bridge
Okay, I see
Individual team members don't have their own sets of live/test mode keys.
The live and test mode key pairs you see apply to the entire account. It's not currently possible to add a team member and grant them access to test mode keys only
If these team members don't necessarily need access to the Dashboard, I recommend looking into using Restricted Keys and sharing these keys with them instead: https://docs.stripe.com/keys#create-restricted-api-secret-key
vivid steeple
I'm thinking about using the new Sandbox feature. I think I can give these roles to developers Sandbox Administrator, Support Specialist, Analyst, Dispute Analyst, and Refund Analyst
And they will still be able to do everything + forward stripe events to their local machine (generating webhook secret keys)
Is that something people do?
wind bridge
Sandboxes would help, I agree, as long as you don't intend for developers to be able to access each others objects
vivid steeple
Alright thanks!