Last updated: .
Simple Workflow Automation, workflow rules for Jira Cloud, runs entirely on the Atlassian Forge platform. Limbus Lab operates no server, database or storage for it, and the app declares no outside address, so nothing it handles leaves Atlassian.
- Simple Workflow Automation overview
- Simple Workflow Automation help centre
- Privacy policy
- Terms of service
- Status
- Contact
What it stores
Everything the app keeps is in Atlassian’s Forge storage for this app, or in Jira itself.
| Data | Where | How long |
|---|---|---|
| Rule settings | In the workflow, saved by Jira with each rule | Until the rule is removed |
| The rule list from the last scan, with each rule’s on or off state and health | Forge storage | Until the next scan replaces it |
| Shared actions, event actions and scheduled actions | Forge storage | Until deleted |
| Run history: time, rule id, work item key, workflow and transition, result, reason, duration and the kind of run-as | Forge storage | 90 days from each run |
| Rule change history: who (account id), when, what changed and where | Forge storage | 90 days |
| Email addresses an admin types as recipients, as part of a rule, shared action or scheduled action | In the workflow for a rule; Forge storage for shared and scheduled actions | Until the rule, shared action or scheduled action is deleted |
| The Atlassian account id of whoever last changed or switched a rule, shared action, event action or scheduled action | Forge storage, with that item | Until the item is deleted |
| Status changes seen, for the missed-run check | Forge storage | 72 hours |
| Markers that stop a retried step from repeating a change | Forge storage | Up to 7 days |
| Loop-guard counters for event and scheduled actions | Forge storage | Until the action is deleted |
| The dry-run and emergency-stop switches | Forge storage | Until changed |
| A “created from” property on work items made by Create work items, if ticked | Jira work item property | With the work item |
| A message from Display message to user | Jira work item property | Shown for two minutes after the move |
What is not kept in run history or logs
- Run history keeps ids, work item keys, results, reasons and durations, not names, email subjects or email bodies.
- Run history never stores email addresses, and the app’s logs hold no names, account ids, email addresses or message text.
- Work item content is read from Jira when a rule runs, and not copied into app storage.
Email addresses
Email addresses an admin types as recipients are stored as part of the rule, shared action or scheduled action they were typed into, until the admin deletes it. For a rule they sit in the workflow, which Jira keeps. For a shared or scheduled action they sit in Forge storage. Run history never stores addresses.
Account ids
The Atlassian account id of whoever last changed or switched a rule, shared action, event action or scheduled action is stored with that item until it is deleted. Rule change history holds account ids for 90 days.
Retention and deletion
How long each kind of data is kept is in the table under What it stores. Run history and rule change history expire after 90 days.
Personal data reporting
The app follows Atlassian’s personal data reporting. When an Atlassian account is closed, the account ids the app stores for it are erased.
How expiry works
Expired rows are removed by the Forge platform, usually within 48 hours of their expiry time.
Architecture
The parts
| Part | What it is |
|---|---|
| Workflow rules | Forge workflow condition, validator and post-function modules, set up on screens inside Jira’s workflow editor. |
| Admin page | A Forge admin page in Jira settings, built with Atlassian’s UI Kit. Only Jira administrators can open it. |
| Work item panels | Post-function errors and rule history on a work item for administrators, a “Why can’t I move this?” panel, and the flag shown by Display message to user. |
| Functions and queues | Forge functions run the post-functions. Longer work, such as sequences, emails and scheduled runs, goes to Forge queues. |
| Triggers | Forge triggers for Jira events (event-based actions and missed-run checks) and for timed work (scheduled actions every 5 minutes, an hourly missed-run check and a daily event check). |
| Storage | Forge storage for this app. See What it stores. |
How a rule runs
- Conditions and validators are Jira expressions. Jira runs them itself, inside Jira, when someone looks at or makes a move.
- A post-function runs in a Forge function after the move. It reads and writes Jira through Atlassian’s APIs, as the person chosen in its run-as setting, and records the run in Forge storage.
- Email is sent through Jira’s own notification API, so mail leaves from your Jira site, not from a server of ours.
No external servers
- No Limbus Lab server, database, file store or analytics service is involved.
- The app’s manifest declares no external fetch address.
- Its only subprocessor is Atlassian, which hosts the Forge platform.
Scopes and permissions
| Scope | Why it is needed |
|---|---|
| read:jira-work | Read work items, comments, links and searches that rules check or act on. |
| write:jira-work | Make the changes post-functions are set up to make: fields, comments, transitions, new work items, links, worklogs, properties, deletes, and sending email through Jira. |
| read:jira-user | Read people, groups and user properties for rules that pick or check people, and match a typed email address to a person. |
| manage:jira-project | Create a missing version or component when a rule is set to, and save project properties. |
| manage:jira-configuration | Read and update workflows: the rule scan, Health, copy and apply, and switching a condition or validator off. |
| manage:servicedesk-customer | Only for Email issue: add a plain email address as a service project customer, so it can be mailed. Used on sites with Jira Service Management. |
| storage:app | Keep rule lists, actions, run history and rule change history in Forge storage. |
The app asks for no external network access.
Acting as a person
Four scopes (read:jira-work, write:jira-work, read:jira-user and manage:jira-project) allow the app to act as a person when no one is signed in. That is how a post-function, event action or scheduled action can run as the person who made the move or as a named person: Jira then applies that person’s permissions, not the app’s.
Run as
- Most post-functions run as the person who made the move by default. An admin can choose the app, a named person, a user field or a template instead.
- If a chosen person cannot be found, the run fails. It never falls back to the app.
- In team-managed projects, post-functions run only as the person who made the move.
- Rules that read group or role members or comments as the app are offered only in company-managed projects.
Who sees what
- The admin page, post-function errors on a work item and the shared-action picker are for Jira administrators.
- A work item’s rule history is shown to Jira administrators and to people who administer that project.
- “Why can’t I move this?” reads Jira as the person who opens it.
Logging
The app’s logs hold no names, account ids, email addresses or message text. Details of what is kept, and for how long, are under What it stores.
Subprocessors
The text that applies to every app is in Subprocessors. What follows applies to this app only.
Its only subprocessor is Atlassian, which hosts the Forge platform. The app declares no outside address, so nothing it handles leaves Atlassian. Email goes out through Jira itself.
Security and fix targets
How to report a vulnerability, and the response and fix targets every app uses, are in Vulnerability Reporting.
Built-in safeguards
- Runs as a person you choose. Most post-functions run as the person who made the move by default, so Jira applies that person’s permissions. See Scopes and permissions.
- Admin page for administrators only. Only Jira administrators can open the admin page.
- No outside address. The app declares no outside address, so nothing it handles leaves Atlassian. Email goes out through Jira itself.
- Short retention. Run history and rule change history expire after 90 days.
Security responsibilities
The shared part is in Security and Incident Response. Besides the responsibilities every app has, this app is responsible for the permission checks in its functions. Vulnerability management, security incident response and disaster recovery are shared, as for every app. The app requests only the Jira permissions (scopes) listed under Scopes and permissions and at installation.
Incidents
Customers affected by a security incident involving their data are notified directly, without undue delay and no later than 72 hours after we confirm a breach affecting their data. A written post-incident summary is shared with affected customers within 10 business days. We report security incidents to Atlassian promptly, as required by the Atlassian developer terms. Current service notes are on the status page.
Accessibility
The company statement is in Accessibility Statement. This is Simple Workflow Automation’s first review of how accessible its screens are, against WCAG 2.2 Level A and AA, made on 15 November 2026 on build 2.20.0, evaluated on a development installation and released as production version 2.2.0. It is a self-assessment by the app’s team, not an independent audit and not a certification. Of the 55 criteria, 26 are rated Supports, 7 Partially Supports, 1 Does Not Support and 21 Not Applicable; none is left Not Evaluated. No screen reader has been used yet.
The fixes below are in the released app: build 2.20.0 is production version 2.2.0 since 15 November 2026.
What is built in
- The admin page is built with Atlassian’s UI Kit, and the rule screens in the workflow editor with components from the Atlassian Design System, so they follow Jira’s own keyboard and focus behaviour.
- Colours come from Atlassian design tokens, so the screens follow Jira’s light and dark themes.
- Form controls have visible labels, and refusals at save are given as text, not by colour alone.
Problems found during this review and fixed
- Rule screen blocks are named groups; a refused field is marked invalid, its error is linked to it, and after a refused save focus moves to the first invalid field (1.3.1, 3.3.1, 4.1.2).
- The save message no longer refers to colour: “Fix the error messages above” (1.3.3, 1.4.1).
- The Required fields screen shows its error under the field (3.3.1).
- At 320 px and 640 px, admin filters and toolbars wrap and wide tables scroll inside their own area, so the page does not scroll sideways (1.4.10).
- The Emergency stop switch uses the large size (2.5.8).
- The message shown after saving an event action closes by itself after about 10 seconds, so it cannot cover a focused field (2.4.11).
- In the Shared action rule screen, focus moves into the editor when it opens and back to the picker when it closes (2.4.3).
- Issue panel headings follow the panel title level (1.3.1).
- Confirmations and short panels on the admin page are now dialogs: focus moves in, Tab stays inside, Escape closes them and focus returns to the button that opened them (2.4.3, 2.1.2).
- The same functions have the same names on the admin page and the rule screens, such as Turn on, Turn off, Delete and Scan workflows (3.2.4).
Known gaps
- With text spacing applied at 640 px, admin tab labels are cut with “…”; the Atlassian UI Kit tabs neither wrap nor scroll (1.4.12, Does Not Support).
- The long New and Edit forms for event and scheduled actions stay on the page; when they are cancelled, focus goes to the page body. Tab or Shift+Tab brings it back (2.4.3).
- The admin tab list has no accessible name (1.3.1).
- The scroll area of a table at 320 px cannot take focus and has no name (1.4.10).
- Row buttons (Edit, Delete, Duplicate, Open workflow) have the same name on every row; the table gives the row (2.4.6).
- The text box inside each select is smaller than 24 px; the whole select is the target (2.5.8).
- Some admin messages, such as “Last scanned just now.” and health results, are not announced (4.1.3).
If something is hard to use, tell us through the contact page, with the subject “Simple Workflow Automation accessibility”. Say which screen, what you use (for example a screen reader, keyboard only or zoom) and what happened. We reply within 3 business days.
Accessibility Conformance Report (VPAT 2.5, WCAG edition)
| Item | Value |
|---|---|
| Name of product | Simple Workflow Automation for Jira, by Limbus Lab |
| Product version evaluated | Build 2.20.0 (commit 3f5cafe), evaluated on a development installation; first review. The same build is production version 2.2.0 since 15 November 2026. |
| Report date | 15 November 2026 |
| Product description | An Atlassian Forge app for Jira Cloud. It adds post-functions, conditions and validators to Jira workflows, configured in the workflow editor, and an admin page with ten tabs for Jira admins. |
| Contact information | Limbus Lab, through the contact page (limbuslab.com/contact/) |
| Evaluator | Simple Workflow Automation team, self-assessment (automated scans, measurements, keyboard testing inside Jira, code review; no screen reader) |
| Applicable standard | WCAG 2.2 Level A and Level AA. WCAG 2.1 Level A and AA criteria are a subset of these tables. 4.1.1 Parsing is obsolete in WCAG 2.2 and is not listed. Level AAA, Revised Section 508 and EN 301 549 tables are not included. |
| VPAT template | VPAT 2.5 (WCAG edition), ITI terminology |
Evaluation methods used
This report is a self-assessment that combines the following. It is not an independent audit.
- An automated scan with axe-core 4.10.2 (WCAG 2.0, 2.1 and 2.2 Level A and AA rules) on the ten admin tabs, from a copy of the page as drawn in Jira, with colour contrast checked.
- The same scan on the 41 kinds of rule screen, from the app’s built code with a stand-in for Jira, in light and dark.
- A markup scan (axe-core 4.14.0) of 164 rule screen states: create, edit, view and refused save. It does not check layout or colour.
- Contrast and size measured in the live Jira page, light and dark, including 1,209 text items on the rule screens.
- Keyboard testing with real key presses on the admin page and in the Jira workflow editor.
- Reflow and text spacing at 320 px and 640 px.
- Each fix checked again on the development installation; where a later check differs, the later result is reported.
- A review of the admin and rule screen code.
Not tested
- No screen reader has been used, on any platform.
- Only five rule screens were opened inside Jira; the others were tested with the stand-in, in the create state only.
- True browser zoom (a 640 px view was used instead), dark theme of open menus and status labels, and actions that would change data (Run now, Turn off, row Delete).
- Issue panels in a browser, phones and other assistive technology.
Scope: the app’s own screens in Jira (the admin page and the rule screens). Jira’s page chrome, navigation, sign-in and dialogs are provided by Atlassian and are outside the app’s control.
Terms
- Supports: the functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: some functionality of the product does not meet the criterion. In this report it is also used where only part of the product was checked; the remarks say which part.
- Does Not Support: the majority of product functionality does not meet the criterion.
- Not Applicable: the criterion is not relevant to the product.
- Not Evaluated: the product has not been evaluated against the criterion.
Table 1: Success criteria, Level A
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | axe-core found 0 image-alt, svg-img-alt and role-img-alt violations on the 10 admin tabs, on 41 rule screens in a browser in two themes, and on 164 rule screen states in jsdom. The only image is a decorative app mark. A person did not judge whether each icon has a suitable meaning. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | The app has no audio or video content. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | The app has no audio or video content. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | The app has no audio or video content. |
| 1.3.1 Info and Relationships | Partially Supports | Rule screen groups are named by their heading, refused fields carry aria-invalid, and error text is linked to its field with aria-describedby (checked in the DOM on 4 of 5 screens tried). Admin tables have labels. axe found 0 label and aria violations. Limit: the admin tab list has no accessible name, because the Atlassian UI Kit Tabs component does not accept one. The Required fields screen was fixed after this check; its aria-invalid and aria-describedby were not read live. Issue panels were not tested live. |
| 1.3.2 Meaningful Sequence | Supports | Tab order matched the visual order in the admin tab panels, the Rename panel and the Matches a format rule screen. Not every one of the 41 rule screens was walked. |
| 1.3.3 Sensory Characteristics | Supports | The one instruction that named a colour was reworded to "Fix the error messages above". Remaining position words such as "below" come with a named control. A person did not read the full text of all 41 rule screens. |
| 1.4.1 Use of Color | Supports | Status lozenges carry text (On, Off, Healthy, Added). Error messages are words as well as red, and delete confirmations use words. |
| 1.4.2 Audio Control | Not Applicable | The app plays no audio. |
| 2.1.1 Keyboard | Supports | Tabs, buttons, inline panels, selects, radio buttons and checkboxes were operated by keyboard. A condition, a post function and a shared action were created entirely by keyboard in the Jira workflow editor. Not every one of the 41 rule screens was walked. |
| 2.1.2 No Keyboard Trap | Supports | Tab and Shift+Tab left every admin panel and the rule screen frame. Escape traps nothing. On version 2.20.0, the dialogs keep Tab inside while open, as dialogs do, and Escape closed all 11 dialogs tried. |
| 2.1.4 Character Key Shortcuts | Not Applicable | The app defines no single-key shortcuts. |
| 2.2.1 Timing Adjustable | Not Applicable | The app has no time limits. Flags can be dismissed. |
| 2.2.2 Pause, Stop, Hide | Supports | The app has no moving or auto-updating content other than a loading spinner. |
| 2.3.1 Three Flashes or Below Threshold | Not Applicable | The app has no flashing content. |
| 2.4.1 Bypass Blocks | Supports | Tested with real key presses on version 2.19.1, within the app's own screens (Jira's page shell is outside the app). On the admin page, the app heading is followed by the tab list, which takes one Tab stop; the first control of the tab content is reached in 3 stops on 8 of 10 tabs, and the Recipes tab has no focusable control. No block of the app repeats before the content. Every tab has a level 1 heading. Rule screens open in Jira's workflow editor dialog and start with their own fields. |
| 2.4.2 Page Titled | Supports | The admin page title is "Simple Workflow Automation - Jira". The rule screen frame is titled "Simple Workflow Automation rule configuration". |
| 2.4.3 Focus Order | Partially Supports | Tested with real key presses on version 2.20.0. Confirmations and short panels on the admin page are dialogs (Where used, Rename, Delete for events and scheduled actions, Run now, Turn off, Dry run, Emergency stop, Export, Copy, Apply): on open, focus moves into the dialog, Tab stays inside it, Escape closes it, and focus returns to the button that opened it, in all 11 dialogs tried. The New and Edit forms for event and scheduled actions are still shown inline in the page; when one is cancelled, focus falls to the page body. In the rule screens, the Shared action editor moves focus to its Name field on open and back to the picker on close. Closing a dialog with its Cancel or Close button (rather than Escape) was not tested. |
| 2.4.4 Link Purpose (In Context) | Not Applicable | The admin page and rule screens use buttons. No text links were found. |
| 2.5.1 Pointer Gestures | Not Applicable | The app uses no path-based or multipoint gestures. |
| 2.5.2 Pointer Cancellation | Supports | Controls are native buttons that act on click. No down-event handlers were found. Dragging off a control before release was not tested. |
| 2.5.3 Label in Name | Supports | axe label-content-name-mismatch reported 0 results on the 10 admin tabs and on 41 rule screens in a browser, in two themes. The create state was tested; edit and filled states were not tested in a browser. |
| 2.5.4 Motion Actuation | Not Applicable | The app has no motion-activated functions. |
| 3.1.1 Language of Page | Supports | lang="en" is set on the Jira page and on the rule screens. |
| 3.2.1 On Focus | Supports | Moving focus alone changed nothing in any walk-through. |
| 3.2.2 On Input | Supports | Typing and choosing options did not submit or move focus. Testing was limited to the controls tried. |
| 3.2.6 Consistent Help | Not Applicable | The app has no help mechanism. |
| 3.3.1 Error Identification | Partially Supports | Rule screens show error text, set aria-invalid, move focus to the first invalid field and link the error with aria-describedby (read in the DOM on 4 of 5 screens tried). On the Required fields screen the inline error text and focus on the field were seen live, but aria-invalid and aria-describedby could not be read because the rule screen is a cross-origin frame. The admin Scheduled name field shows text and aria-invalid but no aria-describedby. Some admin messages use SectionMessage, which cannot be linked to a field. |
| 3.3.2 Labels or Instructions | Supports | axe label rules reported 0 violations on all tested screens. Hints appear under fields. |
| 3.3.7 Redundant Entry | Not Applicable | The app has no multi-step process that asks for the same data again. |
| 4.1.2 Name, Role, Value | Supports | axe aria and name rules reported 0 violations on the 10 admin tabs, 41 rule screens in a browser, and 164 rule screen states in jsdom. aria-invalid is set on Select and Textarea fields. The admin tab list has no accessible name (recorded under 1.3.1). No screen reader was used, so what a screen reader announces was not tested. Edit and filled rule screen states were not tested in a browser. |
Table 2: Success criteria, Level AA
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The app has no audio or video content. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | The app has no audio or video content. |
| 1.3.4 Orientation | Supports | The code has no orientation lock or orientation CSS. The admin page rendered at 320x700 and 640x800 pixels. A device was not physically rotated. |
| 1.3.5 Identify Input Purpose | Not Applicable | The app has no fields that collect personal data. axe autocomplete-valid reported 0 violations. |
| 1.4.3 Contrast (Minimum) | Supports | Computed text contrast on the 10 admin tabs in light and dark themes, and on 1,209 text nodes of the rule screens in both themes: no enabled text below 4.5:1 (3:1 for large text). Only disabled controls were lower, which are exempt. Not tested: dark theme of every open dropdown menu and of lozenge colours on Run history rows. |
| 1.4.4 Resize Text | Supports | At a 640 px viewport (the width of 200 percent on a 1280 px window), every admin tab panel fit its container and the document did not scroll sideways. The Rules table scrolls inside its own region. A real 200 percent browser zoom on a wide desktop was not available and was not tested. |
| 1.4.5 Images of Text | Supports | The app uses no images of text. The only image is the logo mark. |
| 1.4.10 Reflow | Partially Supports | At 320 px every admin tab panel measured 240/240 px and the page does not scroll sideways because of tables. Tables are wider than the panel (402 to 720 px) and scroll inside their own region. That region is not keyboard focusable (tabindex -1) and has no name, so keyboard access to the scrolled part was not shown. The admin tab labels truncate at 320 px; this is a limit of the Atlassian UI Kit Tabs component, which has no wrap or scroll option. The document measured 329/320 px, 9 px from Jira itself. All 41 rule screens fit at 320 px in the create state; step cards with several steps were not tested. |
| 1.4.11 Non-text Contrast | Supports | Light theme: focus ring about 3.6:1, Select border 3.3:1. Dark theme: control borders 4.22:1, focus ring about 8:1, switch track visible. Not measured: the Delete button border and lozenge borders. |
| 1.4.12 Text Spacing | Does Not Support | With the standard text spacing values applied at a 640 px viewport, panel content stayed intact, but the admin tab labels were cut off with an ellipsis (a 62 px box for 113 px of text). The cause is the Atlassian UI Kit Tabs component, which neither wraps nor scrolls its labels. |
| 1.4.13 Content on Hover or Focus | Not Applicable | The app adds no tooltip or hover content. The code has no Tooltip component and no title attributes, and none were seen on any tab. |
| 2.4.5 Multiple Ways | Not Applicable | The admin page is a single page. |
| 2.4.6 Headings and Labels | Partially Supports | Fields and controls have labels (axe label rules: 0 violations). Row buttons in admin tables (Edit, Delete, Duplicate, Open workflow) repeat the same name on every row; row context comes only from the labelled table. The Atlassian UI Kit Button takes text only and no aria props. |
| 2.4.7 Focus Visible | Supports | A 2 px focus ring was seen on tabs, buttons, Select controls, text fields, radio buttons, checkboxes and the switch, in light and dark themes. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports | Focused controls were in view in all runs. The event save flag, which could cover the bottom left of the panel, now dismisses itself after about 10 seconds and did not cover the Save button. Flags on other tabs and other panels were not re-tested. |
| 2.5.7 Dragging Movements | Not Applicable | The app has no dragging functions. |
| 2.5.8 Target Size (Minimum) | Partially Supports | Admin row buttons measure 24 px high, the row checkbox 24 px, tabs 32 px, and the Emergency stop switch 48x28 px. The text box inside each Select measures 3.9x20 px; the Select control around it (160x40 px) is the pointer target. The Atlassian UI Kit has no prop to size that inner box. Row buttons are exactly 24 px with no spacing margin. |
| 3.1.2 Language of Parts | Not Applicable | The app is in English only. |
| 3.2.3 Consistent Navigation | Not Applicable | The admin page is a single page. |
| 3.2.4 Consistent Identification | Supports | Labels were compared in the source of the admin page and all rule screens, and checked live on version 2.20.0 on the Rules, Events and Scheduled actions tabs. The same functions use the same names: Edit, Duplicate, Delete, Save, Rename, Turn on and Turn off, Scan workflows; Cancel closes a dialog without acting and Close dismisses a dialog that only shows information or results. Six earlier differences were aligned in this release. Error titles were compared in the source; rule screen load failures read the same on every screen. |
| 3.3.3 Error Suggestion | Supports | Messages say what to do, for example "Choose at least one status." and "Enter a pattern." Not every message was read. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Deleting an event action asks for confirmation with the text "cannot be undone", and focus starts on Cancel. Delete confirmations on other tabs were not operated. |
| 3.3.8 Accessible Authentication (Minimum) | Not Applicable | The app has no login. Sign-in is handled by Jira. |
| 4.1.3 Status Messages | Partially Supports | Flags are role=alert (read in the DOM on the event save flag). Rule screens use role=alert and live regions (read in the DOM). Admin inline messages such as "Last scanned just now.", health results and SectionMessage errors have no live region, because the Atlassian UI Kit SectionMessage has no live-region prop. No screen reader was used, so announcements were not tested. |
Table 3: Success criteria, Level AAA
Not evaluated.
Summary of ratings
| Conformance level | Level A (31 criteria) | Level AA (24 criteria) |
|---|---|---|
| Supports | 16 | 10 |
| Partially Supports | 3 | 4 |
| Does Not Support | 0 | 1 |
| Not Applicable | 12 | 9 |
| Not Evaluated | 0 | 0 |
Legal disclaimer: this report describes the version named above as reviewed on the report date. It is a self-assessment; no third-party audit and no screen-reader testing has been performed.
AI
Simple Workflow Automation’s documents describe no AI feature, and no AI usage statement has been published for it. Its only subprocessor is Atlassian, which hosts the Forge platform, and it asks for no external network access. The company rules are in the AI Usage Policy.