GROW

config

It must be a specific integration user who replaces the default admin user

This issue is found automatically by CODA.
Time to fix: 30min

Why is this an issue?

When you execute a scheduled job as the admin user, you give that schedule access to all records and tables that an admin user has access to. This could be a problem because the schedule could have access to sensitive data in private databases.

Other users can see the outcomes of the scheduled job and have access to sensitive data depending on the type of scheduled job. (for example: reports or copied records to public tables)

Best practices

When performing scheduled jobs, make sure that the internal_integration_user option is checked and that the user has only limited roles.

This manner, you can ensure that the user will not have access to important or confidential information.