Origami Version 6.2.8: More Security, More Flexibility, More Control

We are excited to introduce Origami Version 6.2.8 – a new release packed with meaningful enhancements designed to strengthen data security, improve the user experience, and give organizations greater flexibility in managing processes, fields, permissions, and collaboration.

In this version, we focused on capabilities that help organizations work in a safer, more accurate, and more efficient way: from advanced protections for system and API access, through improved collaboration in calendars and meetings, to new features that make it easier to build forms, manage information, and handle complex workflows.

In this article, you will find:

  • Security enhancements that strengthen control over system access
  • New capabilities for calendar sharing and synchronization
  • Improvements in managing fields, forms, and workflows
  • New tools for a smoother, more accurate, and more flexible user experience
  • Practical examples of how these enhancements can support your organization day to day

Here are the key updates included in this release:

Share Your Personal Calendar with the Team – Public Calendar Synchronization
Shared time management has never been simpler. You can now synchronize and share external calendars (Google or Microsoft 365) directly within the system. This enables seamless synchronization across devices without the need for repeated logins, centralizes multiple external calendars in one place, and allows for easy and convenient availability sharing among team members.

Step by step:

  1. The user connects to a Google or 365 account (Technical note: a token is created and attached to the user, not the device).
  2. The application imports all calendars linked to the account and updates them automatically.
  3. The user can mark calendars as “public” to allow other users who have access to the entity to view them.
  4. In the calendar, other users can select shared calendars from a dropdown, and events are displayed with the account address instead of “My events”.

How to use:

•Connect to one or multiple external accounts.

•Select calendars to import and share.

•View other users’ calendars within the entity when they are marked as public.

Who is it for:

•Users with multiple devices who need seamless synchronization.

•Teams or entities that need to share availability and calendars.

•Users with multiple external calendars or accounts.

What it solves / Examples:

•Synchronizes calendars across devices without repeated logins.

•Integrates multiple external calendars into one central location.

•Easily shares calendars with teams and tracks availability.

Block System Access by Country – Full Geographic Security

Full control over system access sources for enhanced information security. This is an ideal solution for companies with strict regulatory requirements, preventing unauthorized access and significantly reducing the risk of breaches by automatically blocking login attempts from unwanted countries.

Step by step:

  1. In System Preferences > General Settings > Security Settings, a new option is added to restrict access by country.
  2. The user selects only the permitted countries from a multi-select country list.
  3. The system will only allow logins from IP addresses identified as belonging to those countries.

How to use:

•A system administrator goes to Security Settings.

•Selects the countries permitted for login.

•Saves – now any access attempt from other countries is automatically blocked.

Who is it for:

•IT / Information Security teams who want to restrict access by geographic location.

•Companies with high regulatory or information security requirements.

What it solves / Examples:

•Prevents unauthorized access from unwanted countries.

•Increases system security and reduces the risk of hackers or breach attempts.

•Example: An Israeli company allows logins only from Israel and the US; all other IPs are automatically blocked.

Restrict API Access to Authorized Sources Only – Integration Protection

An additional layer of protection for API users and automated integrations. This feature ensures that API calls come only from trusted sources (such as the company’s internal servers), preventing malicious or uncontrolled use and protecting the system.

Step by step:

  1. The user goes to General System Preferences > General Settings > Security Settings.
  2. Selects the option to restrict API access by IP.
  3. Enters the permitted IP addresses in a multi-value input field.
  4. Saves the settings.
  5. Now, API calls for the user will only work from the registered IP addresses; any other address is blocked.

How to use:

•An API user enters their IP addresses to allow access only from authorized sources.

•Any call from another address will be automatically blocked.

Who is it for:

•API users with high security requirements.

•IT or automation teams who want to ensure the API is accessible only from specific sources.

What it solves / Examples:

•Prevents unauthorized use of the API.

•Protects the system from malicious or uncontrolled calls.

•Example: A system allows API calls only from the company’s internal server addresses; any other call is blocked.

Immediate Alert on Login from an Unrecognized Device – Account Protection

When a login from a new or unrecognized device is detected, the system automatically sends the user an email alert with the login details (OS, browser, IP address, and country). If the access was unauthorized, the user is prompted to change their password immediately, preventing unauthorized entry even if credentials have been compromised.

Step by step:

  1. The user attempts to log in from a previously unrecognized device or location.
  2. The system identifies the login as “unrecognized” and temporarily blocks access.
  3. The user receives an alert email with the attempt details and instructions.
  4. The user clicks the button to go to their profile.
  5. From their profile, they can change their password immediately.

How to use:

•The user receives an email if someone (or themselves) tries to log in from a new source.

Who is it for:

•All system users who want improved account security.

•Especially for organizations with high security requirements or sensitive information.

What it solves / Examples:

•Ensures users are aware of suspicious login attempts.

•Example: An employee logs in from a new device and receives an email alert with the login details. If the login was not theirs, they can go to their profile and change their password immediately.

Hide Internal Fields from Users – Clean and Organized Forms

Design and management flexibility that allows you to display only what is important. This feature reduces visual clutter for end users and allows you to hide internal, calculated, or sensitive information – without losing the data in the system, as it remains accessible to administrators and the API.

Step by step:

  1. When creating or editing a field (in one of the supported field types), the user sees a “Hidden?” checkbox in the field settings.
  2. The user checks the box to mark the field as hidden.
  3. Afterward, the field will not be displayed in regular views or forms, unless configured otherwise to show hidden fields.

Supported field types:

•Reference field

•Formula field

•Metadata field

•Relation / Multi-relation

•User / Multi-user

•Selection / Multi-selection

•Text / Text area

•HTML / WYSIWYG

•Phone / Email / Hyperlink

How to use:

•Users can hide specific fields in views or forms to simplify them.

•Hidden fields are still accessible via API or special admin views if needed.

Who is it for:

•Administrators or advanced users managing entities with many fields.

•Teams who want to simplify forms or hide sensitive/internal information.

What it solves / Examples:

•Reduces visual clutter in forms or boards.

•Allows hiding internal or sensitive information (like metadata or calculated fields) from end users.

Example: Hiding an internal Notes field or a Formula field that performs a calculation only for the system, but not displaying it on public forms.

Navigate to an Address with One Click – Directly from the System to Maps

A smart shortcut for field teams and mobile users. This feature saves valuable time and prevents typing errors, with a smooth and fast transition from the system directly to navigation, from any device.

Step by step

1.The user clicks the icon(*) that appears next to an address field.

2.On a computer: The button opens the address in Google Maps in a new browser tab.

3.If no apps are installed – the address opens in the default browser.(*)The button’s icon is similar to the Relation field icon (the arrow to the related object), but with a location icon instead of the arrow.

How to use:

•The user can navigate to the exact location of the address in the field with one click, without manually copying the address to Google Maps or another app.

Who is it for:

•Any user who needs quick navigation to an address listed in the system.

•Teams with field activities, deliveries, customer visits, etc.

What it solves / Examples:

•Saves time and reduces errors when copying addresses.

•Enables quick navigation from any device – computer or phone.

•Example: A user sees a customer address in the Address field, clicks the button, and it immediately opens in maps – they can navigate via Waze or Google Maps.

Search Records by Unique Identifier – Accurate Linking Independent of Display

Streamlining workflows and advanced search in link fields. This capability enables faster and more accurate work, especially in organizations managing large databases, and significantly simplifies import and automation processes.

Step by step

  1. The user enters a link or user selection field.
  2. In the search field, they can type the Instance ID of the desired instance.
  3. The system finds the instance regardless of the fields defined in the “Select from fields” category in the link field settings.
  4. The search can be used:

•Manually in the field.

•Via Workflow by pushing a dynamic value.

•Via a Webform URL that pre-fills the field with the Instance ID.

How to use:

•The user can quickly find specific instances by ID, independent of the fields defined for display or other filters.

•The Multi-User field allows the same functionality of searching for a user by Instance ID.

Who is it for:

•Management teams and administrators of large instance databases with many records.

•Users who want to copy values to link fields in a simple and uniform way, independent of the fields displayed in the link field.

What it solves / Examples:

•Enables fast work with Workflows or Webforms that fill values automatically.

•Facilitates the import process (you can import the ID into a link field without worrying about spaces or concatenating field values correctly to fill the link field according to its definition).

•Example: A CRM manager can fill a Relation field with a specific customer’s Instance ID, and the system will find the customer immediately regardless of the fields defined for the field or the current view.

Color Table Rows Based on Conditions – Conditional Formatting in Repeatable Groups

Smarter and more dynamic visibility for your data. This feature allows immediate visual highlighting of critical data according to conditions you define, even within complex data structures like repeatable groups.

Step by step:

  1. The user opens the table widget or Sortable List that contains Repeatable Groups.
  2. The conditional formatting rules defined for fields within the repeatable groups will be displayed automatically.
  3. Changes in values or conditions in fields within the repeatable groups will cause an immediate update of the formatting according to the defined rules (e.g., background color, text color, style).

How to use:

•Users define Conditional Formatting rules in the entity’s view.

•Inside the table widget or sortable list, the fields within Repeatable Groups display the formatting according to the defined rules.

Who is it for:

•Users who manage tables or lists with repeatable groups.

•Teams that want to highlight specific values in an immediate view based on defined conditions.

What it solves / Examples:

•Provides visualization of formatting conditions in widgets, even within repeatable groups, which was previously missing.

Define OR Conditions in Forms and Processes – More Flexible Logic

Advanced logic that allows unprecedented flexibility. This feature enables the creation of smart forms and complex automation processes easily, without the need to duplicate settings or compromise on rigid “AND” only logic.

Step by step:

  1. The user goes to the visibility condition settings of a field or a field within a repeatable group.
  2. Chooses to add a new condition with an OR option between existing conditions.
  3. Multiple conditions can be combined so that the field is displayed if one or more of the conditions are met.
  4. The same principle applies to Workflows and notification conditions – an OR can be added between conditions so that the action is executed if one of the conditions is met.
  5. The result is that fields, repeatable groups, or Workflow/Notification actions are displayed/triggered based on OR logic and not just AND.

How to use:

•Users can define complex visibility conditions in regular fields or within Repeatable Groups.

•The OR option allows for higher flexibility in designing forms and processes.

•OR can also be integrated into Workflows to trigger an action or send an alert if one of the conditions is met.

Who is it for:

•Administrators or system implementers who define forms and complex dynamics in fields and repeatable groups.

•Users who want more complex logic in processes.

What it solves / Examples:

•Allows displaying fields or triggering actions in different situations without requiring all conditions to be met simultaneously.

•Example 1: An “Additional Note” field will be displayed if the “Status” field = “Under Review” OR if the “Amount” field > 10,000.

•Example 2: A Workflow to send an alert is triggered if one of the fields in a repeatable group meets a condition – not all fields need to meet it.

In Summary

Version 6.2.8 continues to move Origami forward as a platform that gives organizations more control, more flexibility, and greater confidence – without compromising ease of use or the ability to build smart processes simply.

Whether you are looking to strengthen system security, improve collaboration between users, streamline processes, or give your teams a better day-to-day experience, this version introduces meaningful enhancements worth exploring.

We are excited to keep evolving Origami alongside the real needs of the organizations that rely on it every day.