--- title: "Tulip GxP capabilities" slug: "tulip-gxp-capabilities" updated: 2025-04-09T17:56:53Z published: 2025-04-09T17:56:53Z canonical: "support.tulip.co/tulip-gxp-capabilities" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # Tulip GxP capabilities *Here are the features and company practices that Tulip uses to comply with GxP regulations.* Who can use this feature Users on Enterprise plans. **Stay up to date with the latest [LTS Releases](/r230/docs/lts-releases)!** Tulip works with customers in the life sciences industries. Therefore, we offer a special version of our cloud software that was developed according to the [GAMP 5 framework](https://ispe.org/publications/guidance-documents/gamp-5) under a QMS compliant with ISO 9001:2015. Here is how Tulip complies with typical GxP standards. ## Internal Practices Tulip uses a QMS that was designed in compliance with ISO 9001:2015. Tulip offers an [LTS, or long term support](https://en.wikipedia.org/wiki/Long-term_support), release to support the needs of regulated customers. This is released every 6 months. ## GxP Specifics Tulip uses the term "GxP Mode" to describe the version of its cloud software that is used by customers with GxP requirements. This version provides the following: - Stricter control over app assignments - Stricter controls over app execution - Stricter controls over app editing - Display more explicit Dates - Display IDs alongside Names Here are our practices around different software features required for GxP compliance. ### Access Control Tulip has multiple [user roles](/r230/docs/adding-users-and-managing-user-roles) that allow for different levels of access to Tulip and the [Tulip Player](/r230/docs/how-to-use-the-tulip-player). ### Run Apps on the Shop Floor Stations can only run apps on one Interface (display device) at a time. A device running the Tulip Player automatically logs out when it is transferred away from a [Station](/r230/docs/managing-stations-and-station-groups). The Tulip Player will automatically logout and cancel any running app after a customizable number of minutes of inactivity (with a warning prior to log out). This can be disabled upon request. ### Version Control All apps in Tulip are version controlled. When an app is executed in the Tulip Player, the version number of the app is logged alongside all other app data with each [Completion](/r230/docs/how-to-complete-an-app-1). You can only run "[Published Versions](/r230/docs/creating-and-managing-app-versions)" of Apps on Stations. If you'd like to run a non-published version, you need to click **Run** from the App Editor. Your organization can define which users are allowed to publish specific apps. After the app is published, the Tulip Player at the operator’s workstation will open the latest published version of the app upon the next time that the app is restarted, completed or cancelled. ### Approvals The [Approvals](/r230/docs/how-to-set-up-approvals-for-your-apps) feature allows you to define which Tulip users are required to review a new version of an app before it can be used on the shop floor. Only users with the "Account Owner" role can modify approvals. The latest version of the app must be signed electronically by all approvers before it is published and made available to be used by operators. ### Precise Data All [Activity History](/r230/docs/how-to-export-tulip-activity-data) will include the unique IDs of apps, users, connectors, and dashboards. Unique IDs are also visible in other parts of the platform: - API Token IDs on the **API Tokens page** - Table Column IDs when hovering over a column - Station IDs when viewing app completion data Dates are more explicit in Activity History. Each timestamp is included as text and structured as the following: MMM-DD-YYYY / HH:mm:ss Z Example: Jan-05-2023 / 21:15:21 +02:00 Tulip also provides an audit log for each individual Table Record, which is used to store information about a single batch, material or subassembly. This is displayed in the [Digital Record History](/r230/docs/using-the-record-history-widget-to-view-changes-to-table-records) in an app. ### App Building Permissions By default, only the app creator can edit an app after they create it. They can give [permissions](/r230/docs/how-to-change-editing-permissions-on-individual-apps) to others to edit the app if needed. Apps are also read-only from the Stations page. ### Electronic Signature for Operators Tulip allows operators to sign within apps using [e-signatures](/r230/docs/how-to-use-the-electronic-signature-widget-1) to certify that they have completed the app. ### Added Warnings Before Actions Warning messages pop up for certain actions as extra security and verification. These warnings appear when you: - Delete a station - Delete a station group - Remove an interface (display device) - Reassign an interface (display device) to another station ## Further Reading - [Tulip IT Welcome Guide](https://support.tulip.co/docs/tulip-it-welcome-guide) - [Authorization and Access Control Using SAML](/r230/docs/authorization-and-access-control-using-saml) - [Using LDAP for User Management](https://support.tulip.co/docs/integrating-ldap-with-tulip) **GxP** **Good *X* Practice**. An abbreviation collecting many of the core principles of Life Sciences compliance. *ex-* - *GMP - Good Manufacturing Practice* - *GLP - Good Laboratory Practice* - *GDP - Good Distribution Practice* **Tulip Player** **Tulip Player** is the Windows/Mac executable program where users can run Tulip apps. Tulip player allows you to create a more seamless user experience by removing the need for a web browser, and allows increased IT controls. **Station** **Stations**are a digital representation of a physical place or device in your facility. Stations are 1:1 with **Interfaces (display devices)** running Tulip Player, but Stations can also be assigned **Edge Devices,**Tulip Vision Camera Configurations, Machines,****and more. **Interface (Display Device)** Users interact with Tulip applications through physical devices like touchscreens, PC monitors, mobile devices, and LCD screens. We refer to these as **interfac****es.**Interfaces must be assigned to a **station** in order to run applications. **App Completion** **App Completions**are a mechanism to store immutable data from a Tulip app. When an app is completed, all **Variable's**current values will be stored in the app completions tab.****This completion data can be analyzed in **Analytics.** By default, after a Completion users will be brought back to the **Begin Screen**of your application. This behavior can be adjusted with other **Transition**types. **PublishedVersion** The **Published****Version**of a Tulip app is a complete version of your Application. When an app is ready to be run in production, its logic can be *frozen*by Publishing that app. One application can have multiple published versions. If a **Station**is assigned to run the Published version of an application, it will only see changes when they are published. **Tulip Player** **Tulip Player** is the Windows/Mac executable program where users can run Tulip apps. Tulip player allows you to create a more seamless user experience by removing the need for a web browser and allows increased IT controls. **Table Record** A **Table Record** is a reference to a row in a **Tulip Table**. Table Records can be created either from the Table UI or from with an App Trigger. To edit a record it must be loaded into a **Table Record Placeholder.** **Digital Record History Widget** The **DRH Widget**allows users to review the changes that have occurred to a **Record.**Traceability to changes is critical in a **GxP**Environment. **Electronic Signatures** In regulated environments (GxP) getting a user signature to the accuracy of data is critical for process validation. The **E-Sig Widget**allows users to collect user signatures along with associated metadata.