# Datasource configs should persist across flows **URL:** \ **Category:** Ask a question\ **Created:** [June 5, 2020, 12:06am UTC](https://community.parabola.io/t/datasource-configs-should-persist-across-flows/651 "2020-06-05T00:06:30Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Geoff\_Bowers](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/geoff_bowers/32/93_2.png) [@Geoff\_Bowers](https://community.parabola.io/u/Geoff_Bowers)\ **Post date:** [June 5, 2020, 12:06am UTC](https://community.parabola.io/t/datasource-configs-should-persist-across-flows/651/1 "2020-06-05T00:06:30Z")
It is REALLY annoying that i have to re-configure or re-authorise a datasource everytime i create a new flow. Am I doing something wrong? Is the best approach to this to have a DRAFT flow with a preconfigured set of datasources that I COPY? Why can’t we just register datasources for the organisation and use them in any flow? ---
**Author:** ![sachi](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/sachi/32/10_2.png) [@sachi](https://community.parabola.io/u/sachi)\ **Post date:** [June 6, 2020, 12:05am UTC](https://community.parabola.io/t/datasource-configs-should-persist-across-flows/651/2 "2020-06-06T00:05:23Z")
Hi @Geoff_Bowers - Thanks for your feedback on this. No, you’re not doing anything wrong. Step authorization is controlled at the flow-level right now. We see some customers use different accounts on different steps on different flows, so controlling at the flow-level is what currently seems to work best. Copy and pasting a pre-authorized step into another flow will still require an intermediary authorization step. I agree that we can improve on the authorization management experience, though! If you have any ideas on this, please share under the [feature request topic](https://community.parabola.io/c/feature-requests/12)! ---
**Author:** ![Ben\_Parker](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/ben_parker/32/362_2.png) [@Ben\_Parker](https://community.parabola.io/u/Ben_Parker)\ **Post date:** [June 9, 2020, 2:34pm UTC](https://community.parabola.io/t/datasource-configs-should-persist-across-flows/651/3 "2020-06-09T14:34:55Z")
Personally, this is one of my favorite Parabola features. When working with others in Integromat or Zapier – if I authorize an app for a workflow they have access to so much more for other things. I love the compartmentalization in Parabola. ---
**Author:** ![Geoff\_Bowers](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/geoff_bowers/32/93_2.png) [@Geoff\_Bowers](https://community.parabola.io/u/Geoff_Bowers)\ **Post date:** [June 9, 2020, 11:25pm UTC](https://community.parabola.io/t/datasource-configs-should-persist-across-flows/651/4 "2020-06-09T23:25:50Z")
Compartmentalisation is great. But if we could register credentialed endpoints like a datasource we could also nominate what level of sharing those registered credentials should have. eg. just to the flow, or to the account, etc. ---
**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/brian/32/11_2.png) [@brian](https://community.parabola.io/u/brian)\ **Post date:** [June 10, 2020, 7:56pm UTC](https://community.parabola.io/t/datasource-configs-should-persist-across-flows/651/5 "2020-06-10T19:56:01Z")
I certainly agree Geoff that it would be great to have credentials and API settings saved into configurations that can be re-used, or shared across multiple flows or teammates. This one has certainly come up before, and we have internally talked through how to support these use cases. ---
**Author:** ![Patrick\_Hoban](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/patrick_hoban/32/224_2.png) [@Patrick\_Hoban](https://community.parabola.io/u/Patrick_Hoban)\ **Post date:** [August 25, 2020, 5:21pm UTC](https://community.parabola.io/t/datasource-configs-should-persist-across-flows/651/6 "2020-08-25T17:21:58Z")
Please do something about re-authorizing! This is the single worst thing about Parabola. It’s a huge pain point and takes heavily away from the whole automation aspect, considering how much time I have to spend re-authorizing the workflow just to get it back to where it was.