Personal and shared automation

A scheduled job runs with the authority of its owner, and ownership also determines who can see and receive its results. “Shared” does not mean that every account can inspect or edit another person's job. The optional cronjob plugin must be installed and available to your account to use scheduled automation.

Choose who owns the job

1. Open Automation and create or edit a job.
2. A personal job is created for your account by default. Only administrators see Owner and can choose Everyone for an instance-wide job.
3. Review the schedule, prompt and any destination before saving.

Personal jobs run as their owner's account, including that account's project policy, tool restrictions and plugin access. A managed-project schedule must be personal. An instance-wide job runs with administrator-level instance permissions and normally reports to the notification channel.

Understand access and results

People can see their own personal jobs. Administrators can also see instance jobs, but not other accounts' personal jobs. A personal job usually reports in its own conversation, named after the job. A recurring job created in a direct one-to-one platform chat can report there. A shared-room job does not post results back into that room. Instance jobs normally use the notification channel.

Jobs use the owner's permissions at execution time. If an account loses access to the cronjob plugin, its job cannot continue running. A host shell check on a personal job also requires its owner to remain an administrator; that is checked before each run.

Manage and check

1. Open Automation and review the Owner shown for the job.
2. Use Pause to stop future runs without deleting the job; resume it when appropriate.
3. Check History to see runs and their outcomes.
4. Confirm the result appears in the intended conversation or channel.

For schedule details and access limits, see Scheduling.