Citizen Integrator Solution?
Hello all,
We’re in the process of on-boarding our first Citizen Integrator in the SnapLogic Platform. We’ve previously federated the development of production integrations to LOB developers, but t...
Forum Discussion
My recommendation on this generally depends on how your existing dev/qa/production environments are set up.
Shayne is correct - you can separate the processing infrastructure by Project Space, as well as separating access to data. However, it can become complex to manage the development lifecycle if you have some spaces that do need management, some that don’t need management, some that need a little management (and so on) all in the same org. Possible, but complex.
It might be just plain simpler to put them in their own org. That will let you keep your citizen integrators completely separate from your fully productionised integrations and minimise the risk of, for example, pushing a integration through your development pipeline that doesn’t meet your standards. It will also give you more power to set up your project spaces so that you can have, again as an example, a structure like this:
- Department
- Staff Member
- Staff Member 2
- Staff Member 3
- Department 2
- etc. etc.
