What is a Project on Toko?

Everything you build on Toko lives inside a project — your top-level creator workspace. You make one once and work inside it. It holds your collections, your team, your artwork, and your payout details, so you never have to set those up twice.

Three boxes that nest

Toko has only three big pieces, and they sit inside each other like a set of boxes — with the Generator beside them:

Project · Collection · Vendor

Project — your workshop

Collection Moss Droplets

Spring Sale · vendorMystery Packet · vendor

Collection Fungus Friends

Launch · vendor

Generator sits beside the collections — it makes the art, then exports into one.

A project holds many collections; a vendor is the stall that distributes tokens. On Toko a vendor is project-scoped, so one vendor can hand out tokens drawn from more than one of the project's collections.

A quick way to remember it: a project is your workshop, a collection is a set you made, and a vendor is the stall where people pick one up.

What a project owns

The project owns everything that should be shared across all of your work. Set these up once, use them everywhere:

Shared, project-scoped resources

Team & access

Members and their roles.

Media library

Reusable images and files.

Whitelists

Allow-lists for gated drops.

Beneficiaries

Who receives payouts.

Revenue presets

Reusable split templates.

Vendors

Distribution across collections.

Collections and generators inherit the project context, and a vendor draws on the project's whitelists, beneficiaries and revenue presets — so a change in one place doesn't quietly break another.

Starting out: the Studio

The Studio is the door into your projects. From there you create a new project — it needs a name, a description, and a thumbnail — or open an existing one. Studio may cap how many projects you can have; when you've reached the limit, the “Create new project” button is disabled with a short explanation.

Why it's built this way

Each box owns the things that should be shared at its level. A project owns what every collection needs (team, media, whitelists, beneficiaries, vendors). A collection owns the promises that apply to a whole set (its attributes, rarity model, supply). A vendor owns the details of one drop (its price, schedule, who's allowed in). This nesting means you never repeat yourself, and changing a vendor never touches the collection behind it.

In short

Project = your top-level workspace; you create it once and work inside it.
It nests: Project → Collection → Vendor, with the Generator beside, feeding art into a collection.
The project owns the shared resources: team, media, whitelists, beneficiaries, revenue presets, and (project-scoped) vendors.
You enter through the Studio; a new project needs a name, description and thumbnail.
Each level owns what's shared at that level, so you never repeat yourself.