Use Workspace Settings to manage the default behavior, configuration, access, and automation rules for your Epsilon3 workspace.

Settings are grouped into four main areas:

Workspace includes General, Notifications, Units, Locations, Acronyms, Integrations, and Export/Import.

Users & Access includes Users, Roles, Skills, and Audit.

Configuration includes Tags, Projects, and Custom Fields.

Rules & Automation includes Runs, Procedures, Release, and Workflows.

Use the Search all settings field at the top of the settings menu to quickly find a setting by name.

Workspace

The General page contains workspace-wide preferences that affect how information is displayed, how schedules are calculated, and how certain workspace-level features behave.

The Workspace Name section displays the current workspace name, the Epsilon3 version, the section label format, and the workspace timezone.

The workspace name is the name users see when they are working in the workspace. Updating this name changes the display name for all users.

Section labels can be displayed as either letters or numbers. This controls how sections appear throughout procedures and runs.

After changing the section label format, the update applies immediately across procedures and runs.

The workspace timezone controls how timestamps are displayed throughout Epsilon3.

Once saved, timestamps display in the selected workspace timezone. When hovering over a timestamp, users can also see their local time and UTC.

General Preferences control workspace-wide behavior.

Display additional details in notifications adds more specific information to notifications, such as names of procedures, parts, or other relevant records. When disabled, notifications are more generic.

Release will be disabled if there are any unresolved actions prevents a procedure from being released while unresolved actions remain, such as comments or redlines. Once all actions are resolved, release becomes available again.

Enable labor time tracking turns on labor time tracking for the workspace.

Addresses are saved internal company locations that can be selected when creating purchase orders.

To add an address, click Add New Address, enter the address details, and save. Once added, the address can be selected as a shipping address when creating a PO.

Workspace Admins can set a default currency and number format for the workspace. This sets the currency and number format shown on orders, items, and accounting throughout the workspace, so teams see consistent, locale-correct formatting everywhere money appears.

Click the pencil (Edit) icon next to Default Currency, select the desired currency and number format from the dropdown, and click Save.

Each option shows the currency, code, region, and an example of how amounts will be formatted (for example, "US Dollar — USD $ · United States · $1,234,567.89").

Working Hours define the standard weekly schedule used for workback schedule calculations.

Each day can be enabled or disabled. For enabled days, enter the standard start and end time. Epsilon3 calculates the total hours for each day and displays the weekly total.

To edit working hours, click the edit icon in the Working Hours section, update the schedule, and save.

Schedule Exceptions are used to account for days that do not follow the standard weekly schedule, such as holidays, closures, or special working days.

To add an exception, click Add Exception, select the applicable date or schedule change, and save.

Exceptions are organized by year.

Default Durations set fallback time estimates for entity types used in workback schedule calculations.

Default durations can be set for:

Procedure Runs
Purchase Order Approval
Inbound Shipment
Inspection

To update these values, click the edit icon, enter the desired duration in hours, and save.

The Notifications page controls which event notifications are sent through each available notification channel.

Notification channels include:

In-App
Email
Realtime Client
Slack DM

Notification categories are grouped by event type, including General, Runs/Procedures, Builds, Issues, and Other.

Click the arrow next to a category to expand it and manage more specific notification events within that group.

Use the checkboxes to enable or disable each notification channel. A checked box means notifications are enabled for that channel. A minus icon indicates that only some notification types within that category are enabled.

The Units page is used to create and manage custom units used throughout the workspace.

Each unit includes a name, plural form, and abbreviation.

To add a unit, click Add Unit, enter the unit details, and save.

See this article for more information: Units

Locations define physical or logical places where parts, inventory, work, or other workspace items may be organized.

The Locations page displays each location by code and name. Locations can be nested, expanded, searched, sorted, and managed from the row actions menu.

To add a location, click New Location. Enter the location code, name, and any required parent location details, then save.

Use the search field to quickly find an existing location.

See this article for more info: Locations

The Acronym Dictionary gives teams a shared place to define acronyms used across the workspace.

Each acronym can include:

Acronym
Definition
Category
Description
Updated date

To add an acronym, click Add Acronym, enter the details, and save.

To import acronyms in bulk, click Import CSV and upload a properly formatted CSV file.

See this article for more info: Acronyms Dictionary

The Integrations page contains available partner integrations and API options.

Partner integrations may include tools such as Box, COSMOS, Duro, Flow, Jama, Jira Software, LabVIEW, QuickBooks, SAP, Slack, Teamcenter, and Valispace.

Available actions depend on the integration. Some integrations can be installed directly, while others provide additional details.

Use the Partner Integrations tab to view available integrations.

Use the API tab to access API-related configuration and generate an API Key.
See this article for detilas: Generate API Key

The Export/Import page is used to move workspace data.

Export Workspace generates a .e3export file containing data for the current workspace.

Click Export to create a new export. Recent exports appear in the Recent Exports table with creation time and status.

Import Workspace allows Admins to import another workspace’s .e3export file into the current workspace.

Click Import, select the export file, and follow the prompts to complete the import.

Users and Access

The Users page is used to manage workspace members, seats, access, and status.

At the top of the page, Epsilon3 displays workspace seat and user status summaries, including paid seats in use, available seats, active users, invited users, inactive users, and total users.

The user table includes each user’s:

User
Paid Seat
Roles
Groups
Skills
Project Access
Status

Use the search field and filters to find users.

To invite users, click Invite Users.

To bulk edit users, select one or more users from the table. Available bulk actions include editing workspace roles, editing project roles, deactivating users, and re-inviting users.

See this article for more details: Users and Role Based Permissions

Roles control workspace permissions and responsibilities.

The Roles page displays each role by code, role name, required skills, and permission levels.

Permission levels include:

View
Operate
Edit
Admin

To add a role, click New Role, enter the role details, define permissions, and save.

See this article for more details: Role Based Permissions

Skills are used to track qualifications or requirements that can be associated with roles.

The Skills page includes Active and Archived tabs.

Each skill can include:

Name
Code
Description
Expiration schedule
Renewal method
Required roles

To add a skill, click New Skill, enter the skill details, and save.

Skills can also be imported in bulk via CSV.

See this article for more details: Skills

The Audit page is used to generate reports for security, user activity, and workspace history.

Available reports include:

Event History generates a CSV report that includes security-related events for the selected period.

Login Activity generates a CSV report showing login activity by user for the selected period.

User Report generates a CSV report with billing and security-related information for all users in the workspace.

Pending Actions Report generates a CSV report of pending step actions for running procedures in the workspace.

Procedures Report generates an XLSX report including all procedures and general procedure information.

To generate a report, select the applicable date range when available, then click Generate Report. Recent reports appear under Recent Reports.

See this article for more details: Audit

Configuration

Tags help categorize and filter items throughout the workspace.

The Tags page displays each tag with its status, recent usage, all-time usage, created information, and updated information.

To add a tag, click Add Tag, enter the tag details, and save.

Use the search field to find existing tags. Use row actions to manage individual tags.

See this article for more details: Tags

Projects have moved out of Settings.

To manage projects, go to Planning > Projects in the main navigation.

Custom Fields allow Admins to define additional structured fields for workspace records.

The Custom Fields page displays each field’s display name, field ID, description, and field type.

To add a field, click New Field, choose the field type, enter the field details, and save.

Field types may include options such as text fields and custom lists.

See this article for more details: Custom Input Field Management

Rules and Automation

Run settings control the default behavior of running procedures.

Operators automatically participate in running procedures turns participation on automatically when an Operator opens a run. When disabled, the Operator must manually turn on participation before interacting with the run.

Automatically collapse steps that cannot be completed by any role keeps the run view cleaner by collapsing locked steps that no current role can complete. These steps can still be expanded manually.

Update telemetry data even when steps are collapsed allows telemetry streams to continue updating even when the related steps are collapsed.

Require confirmation for sending commands adds a confirmation step before a command is sent.

Automatically collapse step activity when opening a run collapses activity such as signoffs and revoked signoffs by default. Users can expand the activity again when needed.

Allow signing off with PIN allows users to complete signoffs using a PIN.

(See this article for more info: PIN Signoff

Disable comments on ended runs prevents users from adding comments after a run has ended.

Require a comment to skip or fail a step requires Operators to enter a comment when skipping or failing a step.

Failed commands auto-fail a step automatically marks a step as failed when a command in that step fails.

Redline settings control how suggested edits and added steps behave in running procedures.

Allow adding steps to running procedures allows Operators to add steps to a procedure while it is running. See this article for more info: Adding Steps to a Run

Require approval for new suggested edits means suggested edits are not automatically incorporated into the run. They must be reviewed and approved before they are included.

When disabled, suggested edits are automatically included.

Sync redlines between runs on the same procedure version makes redlines available across actively running instances of the same procedure version. This setting requires approval for new suggested edits to be enabled. Each run still determines whether to include the redline.

See this article for more info: Suggested Edits

Pause Reason controls whether users must provide a reason when pausing a run, section, or step.

Options include:

Off
Optional
Required

To add a pause reason, enter the reason in the New pause reason field and click Add.

Procedure settings control default behavior for procedure creation and procedure-level configuration.

Auto generate procedure ID automatically creates procedure IDs.

Only allow Admins to update procedure, run, and release settings restricts those settings to Admin users.

Only allow Admins to update run and release settings restricts run and release settings to Admin users.

Limit ‘Find and Replace’ to one procedure at a time prevents find and replace from being applied across multiple procedures at once.

Require procedures to be assigned a project requires a project assignment before a procedure can be saved or used as configured.

Assigned project must be a subproject requires the assigned project to be a subproject. This option depends on requiring procedures to be assigned a project.

Procedure Custom Fields add additional fields to procedure records.

Click Field to add a procedure custom field.

See this article for more details: Custom Input Field Management

Click Add Step Detail to add custom step-level detail fields.

Custom Lists define reusable list values that can be used by configured fields.

The Custom Lists table displays active and archived lists. Each list includes the list name and available options.

To add a list, click Add List, enter the list name and options, and save.

Release settings control procedure versioning and release approval behavior.

Auto version numbering controls the default version format for new procedure revisions and drafts.

When enabled, Epsilon3 automatically applies the configured major/minor version format. Updates only affect new revisions and drafts.

To update the format, click Edit, configure the major value, delimiter, and minor value, then save.

See this article for more info: Auto Version Numbering

Procedures can be released using either a release flow or a review group. A default can be set to automatically apply to new procedures.

Release Flows define release workflows with review groups for major and minor releases.

Click Add Release Flow to create a new release flow.

Review Groups define the roles required to release procedures.

Click Add Review Group to create a review group.

A review group can include one or more stages. Each stage can require one or more roles. The setting Clear approvals if additional changes are made determines whether existing approvals are removed when new changes are made after approval.

See this article for more info: Review a Procedure and Review Groups

Workflows are automated actions that can be created, tested, paused, archived, and monitored from Settings.

The Workflows page includes a Workflows tab and an Execution Log tab.

The Workflows table displays:

Workflow Name
Status
Action
Executions
Last Triggered

To add a workflow, click Add.

To manage existing workflows, select a workflow or use the row actions menu. Available actions include Run, Pause, Test, and Archive.

Use filters and search to find specific workflows.

See this article for more info: Workflows