#accua-roles-permissions

1 messages · Page 1 of 1 (latest)

native roseBOT
hexed wadi
#

Hi there! No, this isn't currently possible

#

Can you share a bit more about your use case for this? I think the only workaround at the moment is to create a separate account, keep this in test mode (don't activate it), and grant them the developer role in this other account

brave void
#

That’s pretty surprising

#

Slows our workflow down. Maybe it’s just totally not necessary when developing with connect accounts?

hexed wadi
#

Can you provide more context?

native roseBOT
#

accua-roles-permissions

brave void
#

I’m looking into this, it looks like developer roles have access to the api keys as well as some settings (not enumerated), and view only has nothing but the ability to sift through data

hexed wadi
#

Ah, I was wondering what you meant by "not necessary when developing with connect accounts".

brave void
#

Sure, we’re using stripe connect to facilitate money movement and I’m just not sure what changing permissions from dev to view only means for workflows

hexed wadi
#

What workflows exactly?

native roseBOT
brave void
#

working with the cli should be possible so long as there's access to the api keys (even though they won't be accessible through stripe) is that correct?

lethal creek
#

yes they can hardcode the API keys in the CLI.

brave void
#

Ok, so in reality changing permissions from dev to view only means if the api key gets rolled and it’s not updated elsewhere then the dev will have to ask

#

And autonomy over some settings

lethal creek
#

yeah

#

IMO view only is "worthless" for developers

#

it'd be almost the same to not giving them access at all and telling them to have a separate Stripe account to test things

#

It does have some upsides like they can see logs and Events and such, but they will still feel so limited with "view only"