Organizations and Products

GeckoGuard uses a hierarchical structure: Organizations contain Products, which contain Licenses.

Organizations

An Organization is the top-level container for your products, licenses, and team members. Think of it as your company or workspace.

Organization Features

  • Multi-tenancy: Separate organizations for different projects or clients
  • Team collaboration: Invite team members with different roles
  • Isolation: Products and licenses are scoped to an organization
  • Billing: Subscription plans are tied to organizations

Creating Organizations

You can create multiple organizations from your dashboard. Each organization has its own:

  • Products
  • Licenses
  • API keys
  • Team members
  • Settings

Products

A Product represents a software application or service you want to protect with licenses.

Product Configuration

Each product has:

  • Name and description: Identify your product
  • Default policy: License policies that apply to all licenses unless overridden
  • API keys: Keys scoped to this product (optional)
  • Team members: People who can manage this product

Product Policies

Define default policies at the product level:

  • Hardware binding (unlimited, sticky, or limit)
  • IP restrictions (unlimited, sticky, or limit)
  • Concurrency limits
  • Expiration settings
  • Reset budgets and cooldowns

These policies apply to all licenses created for the product, but can be overridden per-license.

Roles and Permissions

Organization Roles

  • Owner: Full control — can delete organization, transfer ownership
  • Admin: Manage products, licenses, team members, API keys
  • Viewer: Read-only access

Product-Level Access

Team members can be granted access to specific products within an organization, with roles:

  • Admin: Full product management
  • Member: Read-only access

Example Structure

My Software Company (Organization)
├── Desktop App (Product)
│   ├── License #1
│   ├── License #2
│   └── License #3
├── Mobile App (Product)
│   ├── License #1
│   └── License #2
└── API Service (Product)
    └── License #1

Best Practices

  1. One organization per company/client - Keep billing and access separate
  2. One product per application - Don't mix different software in one product
  3. Use product policies - Set sensible defaults, override only when needed
  4. Organize by team - Grant product access to relevant team members only