Organizations
An organization in Meno maps to a GitHub organization. It groups that org's projects and the teammates who work on them, so a company's sites and the people who edit them live together in one place — separate from your personal work.
You can work in two kinds of context:
Personal projects — repos under your own GitHub account, just for you.
Organization projects — repos under a GitHub org, shared with your teammates.
Switching organization context
The dashboard shows projects for one context at a time. Use the organization switcher in the dashboard header to choose which one you're looking at: your personal account or any GitHub org you belong to. Picking a context filters the project grid to that org's projects, and new projects you create are placed in the selected context.
When you connect GitHub, the orgs you're a member of appear in the switcher automatically. For more on the dashboard and how projects are listed, see Dashboard.
How teammates get access
Access to an organization's projects comes from GitHub. Anyone you add as a collaborator on the repository — or any member of the GitHub org with access to it — can open the project in Meno and edit it. The visual editor is free for everyone, so there are no editor seats to buy and no per-user upgrade to turn on components, styling, internationalization, or the rest of the toolset. Those are all part of the free editor.
Licensing an organization's projects
Meno's paid plan is the CMS plan, and it is licensed per project, not per user. When a project needs more than the free CMS (1 collection with 3 items), someone activates a CMS license on that project from its directory:
meno-studio license activate <key>The license is written to .meno/license.json and committed to the repository, so it is bound to that one project through its Git root-commit fingerprint and shared by everyone who clones it. Every collaborator on a licensed project gets the unlocked CMS automatically — there are no per-user keys to hand out.
Because the license lives in the repo, keep licensed organization repositories private so the key isn't exposed. Each project is licensed on its own: licensing one of an org's projects does not license the others. See Licensing for pricing and activation details.
Desktop app: organization seats
If your team uses the Meno desktop app, it additionally offers organization-wide seats billed through Polar — a convenience for managing licensing across many of an org's projects from one place, rather than activating each project individually. Seats are managed at the organization level in the desktop app; the standalone meno-studio package uses the per-project license described above.
Organizations are how teams collaborate in Meno. Connect your GitHub org, switch into its context from the dashboard, share repository access with your teammates, and license a project's CMS when you need to grow beyond the free tier.