The Seal Platform
WebsiteGet StartedContact Us
The Seal Platform
  • Website
  • Contact Sales
  • Logging in & System Requirements
  • Get Started Here
  • Moving to Seal
    • Migration
    • Implementation
  • Manage
    • Where do I start?
    • Creating Types
      • Documents
      • Work Done
      • Files
        • Extracting Fields with AI
      • Scripts
        • Writing Scripts with the Seal Module
        • Script Action Buttons
      • Charts
      • Converting Between Types
    • Adding Content and Fields
      • Computed Titles
      • Formatting Text
      • Formulas
      • Numbered Lists
      • Setting Assignees
      • Setting Out-of-Specifications
      • Setting Review Requirements
      • Submission Tables
    • Executing Types: Test Instances
    • Work Instructions
    • Change Sets
    • Active Versions
    • Training
    • API
  • Operate
    • Where do I start?
    • Re-executing Instances
    • Reviewing
  • MISC
    • Glossary
    • Inbox
    • Search Page and Saved Views
    • User Permissions and Roles
    • Tags
    • Github Integration
    • Change Management
    • Seal Changelog
  • Video Guides
    • Creating Templates
    • Creating and Reviewing Instances
    • Sending and Completing Trainings
  • Validation
    • Why do I need to validate my platform?
    • What is needed from my end for validation?
    • How is my system validated?
      • Baseline Validation
      • Configuration Validation
      • Compliance Validation
      • What about IQ, OQ, or PQ?
      • Automatic Revalidation
        • Change Controls
      • How do I know if my system is compliant to a standard?
        • Setting up your System
        • Performing Compliance Validation
    • GxP Validation for enterprise customers
    • Can I download a Validation Report?
      • Software Functionality Verification
    • Common Validation FAQs
  • Product Quality
    • Seal's Guarantee of Quality
    • Product Development Lifecycle
    • Platform Operation Tests
    • Incident Procedure
  • IT & Security Policies
    • Seal's Tech Stack
    • Data Storage and Security
    • Cloud Servers vs On-Premises File Servers
    • Data Backup and Disaster Recovery
    • Disaster Recovery Plan
    • Handling Confidential Data
    • Common IT FAQs
  • Regulatory Standards
    • 21 CFR Part 11
    • EU Volume 4 Annex 11
    • ISO 13485 Medical Devices
    • Clinical Laboratory Improvement Amendments (CLIA)
  • Support
    • Contact us
Powered by GitBook

Copyright © Seal 2025. All Rights Reserved.

On this page
  1. Manage

Where do I start?

Last updated 21 days ago

As a builder, you build templates for your team to fill out.

On the navigation side bar, ensure that you are in .

Seal Types

Everything in Seal is a Type. Types are self contained blobs of JSON data that conform to our schema. The different Types in Seal enables a wide range of templates to be built.

Content Type

Content Type
Description

Page Content

Any information that exists on a page

Script code

Script

Chart

Visualisation

File

An uploaded file, e.g. a Word Document, PDF, Excel file

None

No document or page content

*What defines the Lifecycle of a Type?

All Types have a top level status field. There are two types of entity lifecycle that define the possible status values - continuous and completable. Different Types may follow distinct lifecycles based on their purpose and workflow.

Completable

Completable lifecycles represent a discrete piece of work carried out at a specific time, and therefore are usually not modified once they've been finished. If mistakes are identified, you can make a new revision of the completable entity. The stages are:

Active → Done → In Revision → Revised &#xNAN;Continuous

Continuous lifecycles are designed to be reused and improved over time. Continuous entities have numbered versions - the version number increases every time you publish a new version. The stages are:

Version 1 → Draft → In review → Version 2

View all Types within your Platform in the settings modal, under the 'Types' tab.

Types in Seal:

  • Objects

  • Documents

  • Work Done

  • Files

  • Automations

  • Charts

  • Custom

All types can have associated metadata fields, with each type potentially differing in page content and following a unique lifecycle.

https://github.com/opvia/platform/blob/main/docs/public/manage/broken-reference/README.md