P
PILLARDOCS
Architecture & Access Control• Clerk Organizations

Team Access & Multi-Tenancy

Learn how Pillar Fleet Control utilizes Clerk Organizations to provide seamless team access, isolated multi-tenant boundaries, role management, and multi-facility switching for post-production engineering teams.

1. Shared Dashboard Access Overview

In Pillar Fleet Control, access is organized around your Studio Organization. Rather than sharing individual credentials or passing around server SSH keys, every engineer authenticates with their own identity (via email, SSO, or Google Workspace) and joins your shared organization.

All team members in an organization have unified, real-time visibility into the same storage nodes, tail-latency telemetry, degraded drive alerts, and capacity forecasts.

Boutique Tier

Up to 3 Team Members

Ideal for boutique facilities with a lead engineer and assistant TDs.

Studio Tier

Up to 10 Team Members

For mid-size editorial houses and multi-bay commercial post teams.

Facility Tier

Unlimited Team Members

Unlimited seats for large studio SAN/NAS operations and 24/7 NOC staff.

2. How to Invite Team Members

Organization administrators can invite technical directors, storage engineers, and operations staff in seconds:

1

Open the Organization Switcher

In the top-right corner of the Pillar Fleet Control dashboard, click your active Organization Name or avatar dropdown.

2

Select 'Manage Organization'

Click the settings gear icon or select 'Manage Organization' to view members, active invitations, and permissions.

3

Send Email Invitations

Enter the corporate email addresses of your Storage Engineers, Systems Administrators, or Technical Directors. Assign their organization role (Admin or Member) and click Send Invitation.

4

Instant Unified Access

When an invited engineer clicks the link in their invitation email and signs in, their session automatically binds to your studio fleet with zero manual API key or server token distribution required.

3. Role Permissions (Admin vs. Member)

Pillar provides a unified engineering operational model. All engineers can inspect telemetry and execute remediation runbooks, while billing and member administration are reserved for Organization Admins:

Dashboard CapabilityOrg MemberOrg AdminDetails
View Storage Nodes & Real-Time TelemetryAllowedAllowedReal-time disk latency, pool capacity velocity, and IOPS charts.
Inspect Disk Health, SMART Attributes & Bus PathsAllowedAllowedFull visibility into wear metrics, p99 latencies, and enclosure bay mappings.
Execute Non-Destructive Advisory RunbooksAllowedAllowedRun scrub pause suggestions and disk locator LED identification workflows.
Generate Node Pairing Tokens & Enroll AppliancesAllowedAllowedGenerate 15-minute one-time tokens for new TrueNAS, Unraid, or 45Drives nodes.
Configure Facility Alert Rules & ThresholdsAllowedAllowedUpdate alert email recipients and p99 frame drop latency thresholds.
Invite / Remove Team MembersRestrictedAllowedManaged via Clerk Organization members interface.
Manage Stripe Commercial Subscription & InvoicingRestrictedAllowedAccess to Stripe Customer Portal and subscription tier management.

4. Multi-Facility Switching for Senior Technical Directors

If your engineering team oversees multiple independent facilities, stages, or subsidiary studios (for example, Company Chicago and Company LA), each location can be created as a separate Organization in Clerk.

Zero Cross-Contamination: Each organization possesses its own dedicated pairing tokens, storage nodes, disk telemetry history, and alert routing policies.
One-Click Switcher: Use the organization switcher dropdown in the dashboard header to immediately jump between facility views without logging out.

5. Multi-Tenant Security & Data Boundary Guarantees

Tenant Database Partitioning

PostgreSQL clerk_org_id Foreign Keys

All storage nodes, disk telemetry time-series, scrub alerts, and pairing tokens are strictly foreign-keyed to the studio record matching auth().orgId. Queries are scoped at the database layer.

Zero Cross-Tenant Leakage

Server-Side Session Resolution

Dashboard pages and API routes verify the cryptographic JWT session from Clerk on every request. A user belonging to Studio A cannot view, query, or execute commands against Studio B's storage appliances.

Zero Inbound Node Credentials

Outbound Edge Daemon Token Binding

Engineers do not need root passwords or SSH keys to the underlying NAS nodes to monitor them. Nodes pair via ephemeral one-time enrollment tokens and push metrics over outbound TLS 1.3.

Multi-Facility Switching

Clerk Organization Switcher

Engineers managing multiple facilities (e.g., 'Chicago Editorial' and 'NYC Finishing') can seamlessly switch active organizations from the top navigation bar without logging out.