Organizations

Organizations are the top-level container for all resources in Orvion. They enable multi-tenancy, team collaboration, and resource isolation.

What are Organizations?

Organizations provide:

• Resource isolation: All invoices, flows, and API keys belong to an organization
• Team collaboration: Multiple users can belong to the same organization
• Access control: Role-based permissions control what users can do
• Billing context: Usage and billing are tracked per organization

Organization Structure

When you sign up for Orvion:

1. A default organization is automatically created
2. You become the Owner of that organization
3. Each user belongs to exactly one organization (enforced by database constraint)

Organization Members

Each user belongs to exactly one organization. Each membership has:

Roles

• Owner: Full control, can delete organization, manage members
• Admin: Can manage resources, invite members, configure settings
• Member: Can view and create resources, limited configuration access

Permissions

Permissions are determined by role:

• Owners can do everything
• Admins can manage resources and members (except delete organization)
• Members can create and view resources

Organization Scoping

All resources are scoped to an organization:

• Invoices: Belong to an organization
• Flows: Configured per organization
• API Keys: Scoped to an organization
• Connectors: Shared within an organization

When you make API calls:

• Your API key is associated with an organization
• All resources created belong to that organization
• Row-level security (RLS) enforces organization boundaries

Organization Membership

• Each user belongs to exactly one organization
• When you sign up, a default organization is created for you
• You cannot belong to multiple organizations (enforced by database constraint)
• Multiple users can belong to the same organization for team collaboration

Related Documentation

• Key Concepts - Core concepts overview
• API Keys & Auth - Authentication and authorization