Organizations & Projects

Icon Forge is organized into three levels: organizations, projects, and icon packs.

Organizations

An organization is the top-level container. It represents your company, team, agency, or brand — whatever grouping makes sense for who’s managing the icons.

Each org has a globally unique slug (auto-generated from the name)
Orgs contain projects
Orgs can have multiple members with different roles

If you’re a solo developer, you still create an org — it’s just yours.

Projects

Projects live inside organizations. They group related icon packs together.

A project usually maps to a product, client, or platform. For example, an agency might have one project per client brand. An enterprise team might have one project per product line.

Project slugs are unique within the org
Projects contain icon packs
Projects can have their own styles (in addition to global presets)

Icon packs

Icon packs are the things you actually publish and install. A pack lives inside a project and contains a set of named icon slots.

Pack slugs are unique within the project
Packs have their own workspace (scratchpad + pack panel)
Publishing a pack creates an immutable release that developers can install

The namespace

These three levels combine into the install identifier:

org / project / pack

For example: acme/brand/core-icons

This is what developers pass to the CLI. Each segment comes from the slug of the corresponding org, project, or pack.

Typical setups

Solo developer:

mickey/
  my-app/
    app-icons

Agency with multiple clients:

studio-xyz/
  client-a-brand/
    core-icons
    marketing-icons
  client-b-brand/
    app-icons

Enterprise team:

megacorp/
  platform/
    system-icons
    navigation-icons
  mobile-app/
    app-icons