Adjust automations to not have the user named from SafetyCulture Integration Builder

Thanks for the feedback Ben.

One technique you might like to try is to create a dedicated user for integrations: 

1. You can create a User with the name you would like to appear e.g. “Automated Workflow”
2. Create a new SafetyCulture Connection in Integration Builder with that user’s API key
3. Use the new connection in those recipes
4. Actions will then appear as created by “Automated Workflow”
5. Notifications can be configured separately for that user
6. Permissions can be configured separately from your own account

Hi Ben,

We are currently designing a new API key system. Our current concept is:

• Admins will be able to manage API keys centrally for an organisation
• Link API key with a special Service User account rather than the User who created it
• API keys will have extended expiry (365 days from last activity)
• API keys will continue to operate if the user who created them is deactivated
• Service User access/ permissions can be individually scoped to restrict data and actions available to the integration
• Attribution of activites (creation of Actions etc) will be attributed to the Service User for that Integration (e.g Created By SuccessFactors Integration or Created By SafetyCulture Integration Builder).

I’m keen to get feedback on this if you have ideas for further improvements/ changes.

Austin, your original workaround to have a dedicated user is exactly what I have been considering.  However, central management of API keys would be helpful. Because the Integration Builder is limited as to who can use it, I will have to create integrations for other users.  Rather than asking for their key, if I could access and label keys for them, it would be much easier.  As you stated, it would also be helpful for deactivated user keys to still work until we replace the user.  I would also like to be able to create keys with specific permissions/access rather than having to create special users or get other users’ keys.  There are situations when we may need data available to all managers of a site or all users of a site, and we have to “pick” a user that meets that criteria currently to get the right key.