Seal is structured as Organisations → Systems → Entities. Organisations are fully isolated tenants — separate users, data, configuration, and audit trails. Data in one organisation cannot be accessed by another. Systems are logical boundaries within an organisation where entities are created and accessed. Users are assigned roles and permissions per system, and can only access systems they are a member of. One system can be granted read-only access into another — but never across organisations. Systems can represent functional areas (QMS, MES, LIMS) or project-level isolation — CDMOs typically create a separate system per client project to enforce data segregation. Within each system, Types define rules, Templates provide starting points, and Instances are executed records — all version-controlled through change sets.Documentation Index
Fetch the complete documentation index at: https://docs.seal.run/llms.txt
Use this file to discover all available pages before exploring further.
Admin permissions
There are two levels of admin permissions:- Organization Admins - Organization Admins can create systems, add and remove users from systems, and edit user permissions within systems.
- System admins - System admins can edit system settings, such as that system’s homepage and view groups. They also have additional powers within the system, such as bypassing review requirements.
How does access between systems work?
You can configure one system to have read-only access into another. In the system given access, all members will then be able to:- See entities from both systems in views and the search page
- Reference entities from the other system
- Create entities from types/templates belonging to the other system into submission and reference fields.