Organization Management

Organization Management

Overview

In ACT 3 AI, an Organization is the central unit for billing, permissions, storage, and collaboration. Each Organization contains:

• Projects
• Members and their roles
• Subscription plan and credit pool
• Storage allocation
• Billing information

This model is similar to GitHub and Figma, allowing clear separation between personal and team workspaces.

Key Concepts

• Organization – Legal and operational owner of projects and assets.
• Project – Always belongs to exactly one Organization; credit usage is charged to that Organization’s credit pool.
• User – Can belong to multiple Organizations, each with separate billing and storage.

Automatic Creation

• Upon sign-up, a personal Organization is created:
  • Name format: "<User Name>’s Personal Projects"
  • Fully functional; can be upgraded to paid tiers at any time.

Multiple Organizations

• Users can create multiple Organizations to:
  • Separate personal vs. professional work
  • Create client-specific workspaces
  • Manage multi-production teams
• Switching Organizations is done via the account menu.

Roles & Permissions

Role	Capabilities
Owner	Full control: manage plan, edit roles, invite/remove members, transfer ownership
Billing	Update payment details, view invoices, manage VAT info
Creator	Create/edit projects, consume credits
Viewer	View projects/outputs without consuming credits

Notes:

• Only Owners can change subscription plans or transfer ownership.
• "Use Credits" toggle controls whether a member’s actions deduct from the credit pool.

Invitations & Access

• Invitations are sent via email.
• LinkedIn SSO is required for free/Starter plans to prevent duplicate accounts.
• Role-specific permissions are applied upon acceptance.

Credit & Storage Management

• Credits: Shared across the Organization
  • Meters show monthly allocation and rollover bank.
• Storage: Quota based on plan
  • Example: Creator = 100 GB, Studio = 500 GB
  • Overages trigger upgrade prompts.
  • Tools: "Delete all videos (project)" and "Delete all videos (org)".

Archiving & Downgrading

• Archive Plan:
  • Preserves scripts/text assets
  • Deletes video assets 30 days after cancellation
  • No new generations allowed while archived
• Downgrade Workflow:
  • Bulk-delete media before switching to Archive

Security & Governance

• Role-Based Access Control (RBAC) enforced middleware-side.
• All sensitive actions (upgrades, card changes, deletions) require recent re-authentication.
• Organization IDs secure API calls to ensure isolation.

Best Practices

• Use separate Organizations for clients with distinct billing.
• Regularly review member roles.
• Set storage alerts before hitting quota.
• Delegate the Billing role in large teams.

Future Enhancements

1. Consolidated billing for multi-org enterprises.
2. Marketplace revenue share for third-party models.
3. Automatic regional tax/VAT calculation.
4. Educational credit grants without subscription.
5. Self-hosted servers with credit key usage.