Agent Library Copied!
Purpose: This article explains where your existing workflows live in the Agent Library, how to move agents into folders, how folder roles and permissions work, and how workflow Properties and Segregation of Duties (SoD) apply.
Legacy Workflows Copied!
All of your existing workflows are in the Legacy Workflows tab. Nothing about how they run has changed, so you can keep working in them there or move them into folders when you’re ready.
Viewing an agent
To view, run, or edit an agent from the Legacy Dashboard, select the kabob menu (⋮) to the right of the agent, then select View. View opens the agent on the Canvas, where you can edit and run it.
Move Agents to Folders Copied!
Create a folder
To create a folder, you need to be a FloQast Admin. When you create a folder, you automatically become an admin of that folder.
- Select + Add Folder at the bottom of the folder list in the left panel.
- Enter a name for the folder in the Create New Folder window.
- Select Create Folder.
Move an existing agent to a folder
Once you have a folder, you can move existing agents into it from the same kabob menu (⋮).
- Select the kabob menu (⋮) on the agent you want to move.
- Select Move to Folder.
- Choose the destination folder and confirm.
You can only move an agent to a folder where you have admin access.
Archive a folder
Folder admins can archive a folder. Archiving removes the folder from the left panel. Folders can’t be deleted, and an archived folder can only be restored on request, so reach out to your FDA if you archive one by mistake.
Folder Roles and Permissions Copied!
Each folder has its own access list. When you create a folder, you are the only person with access to it. Anyone else needs to be invited before they can open it. Admins can invite team members to the folder and set their permissions via the 'Add' button at the top.
Roles
The Role controls folder visibility and editing rights. There are two roles:
- Admin: Has access to both the Agents and Permissions tabs. Admins can invite users, set their role, and designate whether they can build and/or approve agents built with Segregation of Duties toggled on.
- User: Can view the Agents tab.
Permissions
Builder and Approver are permissions, set per person, by a folder admin, with the checkboxes next to their name.
| Checkbox | View and run agents | Create and edit agents | Approve a version, Draft to Live |
|---|---|---|---|
| Neither checked | ✓ | ||
| Builder | ✓ | ✓ | |
| Approver | ✓ | ✓ |
Approvers can approve a version that a different builder submitted.
Workflow Properties Copied!
Workflow Properties are in the settings of an existing agent. Open the agent on the Canvas and select the cog wheel in the top right. The Properties panel has two tabs: Summary and Permissions.
Summary tab
Summary shows the basic details for the workflow:
- Title
- Description
- Owner
- Created by
- Last Edited
- Status
- Last Run
Permissions tab
The Permissions tab in Properties shows which Close Entities the workflow supports.
- You can add entities to a workflow.
- Once an entity is assigned, you can’t remove it from that workflow.
- To get a workflow without an entity, clone the workflow and set up the clone with the entities you want.
When you clone, the folder list only shows folders where you’re a Builder. If you aren’t a Builder in any folder, ask a folder admin for Builder access.
Note: This is separate from the folder-level roles and permissions above. Those control which people can work in a folder. The Properties Permissions tab controls which entities a single workflow supports.
Version history
Version history lists each version of an agent as a tile, with the newest at the top (Version 4, Version 3, and so on). Expand a tile to see each save, numbered like 4.0, 4.1, and 4.2, with the date and the version it was created from. A green Live badge marks the version that is currently running.
Segregation of Duties (SoD) Copied!
Segregation of Duties (SoD) is a feature you can toggle on within an agent. It keeps one person from both submitting and approving the same workflow version. The check applies to the person who submitted the version.
- A submitter can’t approve their own submission. Someone else with the Approver permission has to.
- A builder can approve a new version of their agent only if someone else submitted it and the builder has the Approver permission enabled.
- A rejected version is final and can’t be resubmitted as is. Editing the workflow creates a new preview, and that preview can be submitted.
- Publishing closes out the major version. The next save moves to the next major version.
Questions about folders or access? Reach out to your FDA or support@floqast.com.