Resources & hierarchy
Access in Panomics is granted to principals (Users, Teams) on specific resources and enforced for those principals at the resource level. Resources have the option to edit access in their detailed view.
Available resources
Resources with editable access currently include:
Organization - With a special edit space in each team's details
Project - Contains analyses and assets
Analysis - Individual computational workflows
Bio-Apps - Reusable analysis applications
Hierarchy example
Organization → Project → Analysis
Access inheritance
Resources in Panomics have a parent-child relationship (e.g., Project → Analysis). This enables you to define access rules at the parent level that apply to all children.
Use Case Example:
You want the "Biologists" team to have access to view all project information on Project A, but also access to view results and run commands in all analyses (present and future) that exist as part of Project A. You achieve this by granting analysis access actions to this team at the Project level → which are then inherited automatically to all its Analysis children.
Last updated