New to Epsilon3?
This guide will teach you how to navigate and organize your Epsilon3 workspace. We'll cover general usage and terminology, best practices, basic settings, helpful links, and where to go if you have questions. Let's get started!
Note: If you haven't received an email with login instructions, your Epsilon3 Admin needs to add you as a user. Send them this link.
Landing Page
When you log in, you land on your default landing page, which displays your Notifications and your Tasks. Return here at any time by clicking the Epsilon3 logo in the top-left corner of your screen.
From the Tasks panel you can add a task with + Add Task, set its priority (Low, Medium, or High), assign it to a user, check it off when complete, and filter the list. Tasks can also be associated with the Shift Log — from a shift log entry, use Create or link task to attach a new or existing task.
Runs
Click Runs to see your Running and Ended procedures. Use the Search Runs bar to find a specific Run by name or ID. You can also Filter Runs by Projects, Locations, Tags, Operations, or Type, and Group them by Upcoming Locations, Project, Status, or Type.
Tip: Training your team to always attach Procedures to Projects makes it much easier to keep your workspace organized and find the Runs you're looking for.
Library
The Library, in the left navigation, is where your team's content lives — including Procedures and Snippets. It's where you create, edit, review, release, and run procedures.
Procedures
The Procedures tab lists every procedure by state — Active, Archived, and Templates. Only released procedures can be run: if there's no released (reviewed & approved) version, the Run option is greyed out, and if there's a newer, un-released version, you'll see Edit Draft in the State column.
Note: We'll cover how to create and run procedures later in the guide.
Snippets
Under Snippets you can create and save Step and Section templates to plug into procedures — saving time and ensuring consistency while building new ones. Read more in Content, Step, and Section Snippets.
Settings
You must be an admin to view Settings. If you don't see this option, skip ahead to the next section. Settings is where admins configure options that apply across multiple procedures or the whole workspace. It's organized into four areas:
Workspace — general workspace configuration: General, Notifications, Units, Locations, Acronyms, and Integrations.
Configuration — Tags, Projects, and Custom Fields. (Projects now lives under the Planning tab; the Settings entry currently just redirects there.)
Rules and Automation — Runs, Procedures, Release, and Workflows.
Create New Procedure
To create a procedure, navigate to the Procedures Library and click the blue + New Procedure button.
Tip: Every procedure requires a unique ID, and each released version requires a unique version number. Make sure your team is aligned on how you name and organize procedures. The most organized workspaces enable both Auto generate procedure ID and Auto version numbering.
A procedure is broken into Sections with corresponding Steps that can include a wide range of notes, media, and content blocks requiring inputs, actions, and role-based step Signoffs.
Tip: While a procedure can have unlimited steps and content blocks, avoid extremely long procedures that could slow your team down.
Steps
To learn how to build out steps, see Anatomy of a Step, which breaks down every content block and how to add them. For keyboard shortcuts to copy, paste, and delete content blocks, see Edit Menu Quick Actions.
Dependence
Step dependencies use AND/OR logic to lock steps until others are completed. See Step and Section Dependence.
Conditionals
Conditionals let you set the next action based on the result of the current step — triggered on step completion or failure, or by a selection from a List or Custom List field.
Procedure Settings
Procedure-level settings are separate from the workspace Settings covered earlier in this guide. Access them via the cog icon in the upper-right of the procedure while in Edit / Draft mode. In Procedure Settings you can configure:
Attributes
Owner — the procedure's owner
Project — the project it belongs to (if applicable)
Default View — List or Single Card
Run Settings
Enable Automation
Make Required (Strict Signoff)
Allow Skip Step
Allow Step Repeat
Allow Suggest Edits, with an optional Enable Enhanced Review (require approval for redlines/bluelines in runs)
Start / End & Data
Start Procedure and End Procedure — the role(s) permitted to start and end the procedure (for example, Any Operator)
Data Sources — select dictionaries and/or groups
Release Settings
Release Process — the review/release flow applied to the procedure
Print Header and Print Footer — optional text shown on printed or exported copies
Review and Release
Once a draft is complete, it must go through Review and Release before it can be run.
Review
When a draft is ready, click Review to open the review-stage prompt. Set the version and add reviewers — either specific roles (anyone with that role can sign off) or individual people — then click Move to Review. Review groups are managed under Settings > Rules & Automation > Release (covered in the Settings section above), where they can also be set as a global default that applies to all procedures. While a procedure is awaiting release, it shows the review group that must sign off.
For more, see Assign or Remove Reviewers and Review Groups / Multi-Stage Review / Release Flow. You can also comment during review — start a thread or @mention collaborators. See Review a Procedure, Procedure Review Diffs, and Suggest Edits While Running.
Tip: Add notes to the Review Notes section to tell reviewers what changed.
Release
A procedure version must be released before it can be run — you can't run a draft. When all required signoffs are complete, the Release button becomes selectable.
Being able to release comes down to permissions, not your workspace access level. Regardless of which role or roles a person has, releasing a procedure requires:
View — you must be able to view the procedure you're releasing. This is the root requirement; without it you can't see or act on the procedure.
Approve — if the procedure requires approval, your role must have approval permissions for that review.
Release Procedures — the role assigned to release must have the Release Procedures permission enabled.
Important: If none of your roles can release, you'll see a message saying so. Go to Settings > Roles to view which roles have release permissions — an admin can enable them on a role you already have, or assign you a role that includes them.
Review Groups for Release
You can configure global review groups for release to account for different requirements — for example, major vs. minor version updates. These are set from Settings and apply to all procedures based on the selected release flow.
Running a Procedure
Anyone with View permissions can view and comment on a running procedure. To Participate and sign off steps, you need Operate permissions.
To start a run, open a procedure from the Library and click the Run Procedure button.
Important: Only the most recently released version of a procedure can be run. If the procedure has no released versions, the Run Procedure button is greyed out.
A running procedure can be viewed as List View (all sections and steps listed) or Single Card View (one step at a time) using the buttons at the top of the screen.
For signing off, repeating, and skipping steps, see Run Procedure. You can also add a step in a running procedure as a Redline (suggested for all future versions) or a Blueline (only this run) — see Suggesting Edits While Running.
Helpful Links
Find how-to articles in our Help Center
Access the app at app.epsilon3.io (or app.uk.epsilon3.io on the UK instance)
Visit the Epsilon3 website
See new features in the Changelog
Working with our API? See the API Docs
Green Button
Support is just a green button away. If you need help, click the green button in the bottom-right corner of the application, the Help Center, or the website. Search for articles in the chat, or connect to a live person quickly and easily.














