mikewilliams - customer portal | Stripe Developers | Page 1

fresh saffron May 31, 2022, 8:47 PM

#

hi there!

#

could you share some more details here? i'm curious about your use case for thousands of configs

#

i don't believe there's a limit on the number of configuration, but it may be simpler for your team to maintain dozens of configurations as opposed to thousands/one per connected account

bronze wren May 31, 2022, 9:00 PM

#

The product is an embeddable, customizable widget, which their connected users use to sell subscriptions

#

So depending on where on the site they're embedding it, they might want to enable different products, different features, etc.

#

we could have them do dozens as you say and store them and maintain them in the database, but for now it's easier to create a config each time, we just wanted to clear them out

#

the configs are basically one-time use for the most part

#

The reason we don't just set a base config is that these are for connect clients, so we can't anticipate all the different portal settings they'd want, or even know what they have enabled in their stripe dash

fresh saffron May 31, 2022, 9:04 PM

#

thanks for the context!

#

there's no limit to the number of portal configurations you create

bronze wren May 31, 2022, 9:42 PM

#

so it doesn't affect anything really?

#

is there any reason for us to deactivate them each time

#

does stripe ever clean those up

fresh saffron May 31, 2022, 9:44 PM

#

no, stripe won't remove or clean up these configurations.

#

i think the question comes down to how your team plans on managing the configurations you create. additionally, it's currently only possible to create and list custom portal configurations via the api. if this changes in the future (i.e., if you can view a list of custom portal configurations in the dashboard), then your team may see some delays if/when the dashboard is trying to retrieve all your configurations

#mikewilliams - customer portal