Organization management
An organization is the primary security, billing, operational, and data-isolation boundary in FlaskTrack.
Organization settings
Authorized users can manage the organization name, timezone, members, invitations, roles, access requests, integrations, AI providers, and other deployment-specific settings.
Membership
Every user should have an individual account and an appropriate role. Review pending invitations, remove obsolete access, and avoid shared credentials.
Roles
Owners control the highest-risk organization settings. Admins manage day-to-day configuration and review. Scientists and Technicians focus on authoring or execution, while Viewers receive read-only access. Exact permissions remain server-enforced.
Billing and plan
Billing controls available in the organization depend on the subscription and deployment. Limit billing access to authorized Owners and verify changes in the billing provider and FlaskTrack organization state.
Integrations
Organization settings can contain API keys, AI-provider credentials, and alert destinations. Treat these values as secrets, rotate them after exposure, and test changes with non-production data.
See AI integrations for provider configuration and the built-in assistant, or External AI agents and MCP tool calling for organization-scoped agent integrations.
Compliance ownership
Assign owners for frameworks, checklists, electronic-signature policy, audit review, validation, qualification, incidents, and periodic access review. Product configuration without assigned procedural ownership is not sufficient for a controlled process.
Data isolation
Records, files, API requests, and audit activity are organization-scoped. Never copy organization identifiers or credentials between tenants without an approved migration or support procedure.