Admin settings and governance
Laya WorkflowOS's admin page for Jira admins: emergency stop, AI assist, approvals, editor groups, limits, maintenance windows, blocked actions, audit trail and erasing data.
Last updated
On this page
The admin page is where Jira admins govern automation on the site. Open Jira settings, then Apps, and choose the Laya WorkflowOS admin page in the sidebar. It says Governance & safety · visible to Jira admins only: other people cannot open it, and the app checks the Jira admin permission on every change.
Changes are saved together: the bar at the bottom shows unsaved changes, with Save policy and Reset. The emergency stop is the exception: it saves as soon as you choose it.
Emergency stop (all editions)
Pause all rules pauses every rule on the site: event, scheduled and workflow rules. It takes effect within about 10 seconds, and nothing is deleted. A red banner says automation is paused. Choose Resume all to start again. Admins can still test rules from the app while it is paused.
AI assist (all editions)
Choose the AI assist chip to switch between Enabled (the default) and Disabled, then Save policy. When it is off, nobody can use AI to draft, convert or explain rules, scan for conflicts, find templates or write JQL, search shows only the JQL editor, and reports get no AI summary. Rules, conditions, actions and expressions keep working.
Advanced edition controls
The sections below need the Advanced edition. On Standard you can see them, marked Advanced only, but not change them.
| Section | What it does |
|---|---|
| Rule approval | With Require approval on, a new or edited rule only runs after an admin approves it here. Editing an approved rule, or the actions of a shared sequence it runs, sends it back for approval. Rules created by editors who are not Jira admins always need approval. |
| Who can manage rules (RBAC) | In Editor groups, list Jira group names, separated by commas. Members of those groups can then create, edit, publish and delete rules, as well as Jira admins. Leave it empty and only Jira admins can. |
| Limits & throttles | Caps that stop runaway automation (see the table below). |
| Maintenance window | A weekly window, in UTC, when automation pauses itself, for example during deployments. Pick days, or none for every day, and a Start (HH:MM) and End (HH:MM). |
| Blocked action types | Stops rules from running the action types you pick. Rules keep the step, but it is skipped with "blocked by admin policy". |
| Export policy / Import policy | Save these settings as a JSON file, or load one from another site. An imported policy fills the form; review it and choose Save policy. |
| Audit trail | Who created, edited, deleted, enabled, published or approved a rule, and who changed the policy. Filter it, download it as CSV, or Clear it. |
| Failed runs (dead-letter queue) | Automated runs that still failed after their retries. Replay one, dismiss it, or Clear the list. |
Limits & throttles
| Limit | Default |
|---|---|
| AI monthly token cap | The edition allowance |
| Max export / report rows | 5,000 (the most allowed) |
| Max actions per rule run | 0 |
| Max issues per scheduled run | 50 (up to 1,000) |
| Max rules total | 0 |
| Max runs / hour per rule | 0 |
| Error alert threshold (24h) | 0. When set, a banner warns when rule errors in the last 24 hours reach it. |
| Audit retention | 500 entries (50 to 2,000) |
Overview and recent errors (all editions)
The page shows how many rules there are, how many are enabled, errors in the last 24 hours and AI tokens used this month. Recent rule errors lists the latest failures, with the rule, issue and error.
The app's Settings page
Inside the app, Settings shows the edition, hosting and permissions under About, the AI meter under AI usage & limits (where an admin can Set lower cap), and Backup & migration for exporting and importing rules.
Erase data and uninstall
- Danger zone, erase all data permanently deletes everything the app keeps for the site: rules, run logs, the audit trail, settings, shared sequences, saved searches, exports and failed runs. Type ERASE and choose Erase all data. It cannot be undone.
- Uninstalling the app runs the same purge automatically.
- Export your rules first from Settings, Backup & migration, if you might want them again.
Email support@laya.net and include what you expected, what happened, and a link to the affected board or item so we can help quickly.