🧬 Flask Track Docs

Organization Management

Organizations are the foundational security, operational, and compliance boundary within Flask Track.

Every record, workflow, audit event, and operational action belongs to an organization.

Organizations control:

Flask Track is designed for multi-user laboratory environments where accountability, traceability, and operational separation are critical.

What an Organization Represents

An organization typically represents:

Organizations isolate data and operational activity from one another.

Users only have access to organizations they are explicitly assigned to.

This ensures:

Organization Scope

All major platform entities belong to an organization, including:

Organization ownership is enforced throughout the platform.

Organization Overview

Each organization contains:

The organization acts as the central operational container for all laboratory activity.

Members & Access Control

The Members section displays all users associated with the organization.

For each member, Flask Track may display:

Membership determines what operational and administrative actions a user may perform.

Roles

Roles define a user’s permissions within the organization.

Permissions are enforced across:

Owner

Owners have full organizational authority.

Typical capabilities include:

Owner access should be assigned sparingly.

Admin

Admins manage day-to-day operational and administrative workflows.

Typical capabilities include:

Admins generally cannot perform restricted ownership-level actions.

Scientist

Scientists manage scientific workflows and operational data.

Typical capabilities include:

Scientists generally cannot manage organizational users or ownership-level settings.

Technician

Technicians focus on operational execution.

Typical capabilities include:

Technicians typically have limited administrative access.

Viewer

Viewers have read-only access.

This role is commonly used for:

Viewers can inspect records and reports without modifying operational data.

Member Status

Each member has an account status that controls organizational access.

Active

Active users can:

Deactivated

Deactivated users:

Flask Track strongly prefers deactivation over deletion to maintain traceability and audit integrity.

Inviting Members

Authorized users may invite additional organization members.

The invitation process typically includes:

  1. Entering the user’s email address
  2. Selecting an initial role
  3. Sending the invitation

Invited users appear in the Pending Invites section until the invitation is accepted.

Once accepted, the user becomes an active organization member.

Pending Invites

Pending invitations allow administrators to monitor outstanding access requests.

Administrators may:

Pending invites help maintain visibility into organizational access management.

Organization Settings

Organization settings control shared operational and administrative configuration.

Depending on deployment and permissions, settings may include:

Organization metadata is referenced throughout the platform.

Billing & Subscription Management

Some deployments include subscription and usage management functionality.

Billing systems may include:

Billing access is generally restricted to organization owners.

Compliance & Audit Ownership

Organizations are tightly integrated with Flask Track’s compliance and audit systems.

Every operational action is associated with:

This ensures laboratory activity remains attributable and reviewable.

Audit Attribution

Audit systems preserve:

Even if users are later deactivated, their historical actions remain preserved.

This is critical for:

Operational Isolation

Organizations are fully isolated from one another.

Users cannot access:

This isolation model supports:

Automation & API Ownership

Automation systems and integrations are scoped to organizations.

This may include:

This ensures integrations remain securely isolated between organizations.

Best Practices

Recommended operational practices include:

Strong organizational management improves both security and audit readiness.

Security Model

Flask Track enforces permissions at both the interface and server level.

Even if a user manually attempts restricted actions:

This defense-in-depth model helps protect sensitive laboratory and compliance data.

Summary

Organizations provide the operational and security foundation for Flask Track.

They enable:

By organizing all operational activity around organizational boundaries, Flask Track supports complex laboratory environments without compromising traceability, reproducibility, or control.