Skip to main content

We have several licenses in our company.  I recently wrote a recipe, and it was working flawlessly, but then my admin access was removed and the recipe stopped functioning.  As soon as my admin access was restored, the recipe immediately kicked back on.  

Is there a way to save recipes to the organization and not to a PERSON so that this never happens again?  Additionally, this would create a fail-safe should an admin leave unexpectedly, and we would then lose all their information.

Having this important process governed by an employee is a potential for disaster, as the scenario I’m talking about demonstrates.

Thank you.

@sheila.smith was your admin access removed from GUIDEcx or from the system you were connecting to through the recipe? Since recipes operate through connectors and connectors are authenticated via API keys that are general to the organization instead of user-specific, I would expect the recipes to already work in the way you are proposing. 

Great question @sheila.smith! I believe that there’s no setting to allow for a “global admin” to use those credentials to authenticate to other apps. 
Might I suggest a best practice: Create a spreadsheet that your team can access to see who’s credentials are used to authenticate to which apps. 

 

Something like this:

 

Reply


Terms & ConditionsCookie settings