Skip to main content

Install your first marketplace item

The Marketplace is where you add capability to Aglyn that you didn't build yourself: plugins, ready-made site templates, themes, layouts, components, dataset schemas and email templates. This guide walks the whole loop once — find, install, use, upgrade, remove — clicking every step.

No code, and nothing you can't undo. The only decision worth slowing down for is which sites it lands on, and step 4 is entirely about that.

Plan availability

Free to browse and install. Individual listings may cost money — the button says so before you buy. Publishing your own listing is a separate thing and needs Pro; see Publish a plugin.

Before you start​

You need an organization with at least one site, and a role that can install. By default that's owner, admin and editor — installing is treated as content work, not an account setting. Viewers cannot, and a custom role can only if it carries the Install plugins permission.

If the Marketplace opens but the Install button doesn't, that's the role, not the plan — see Teams & roles.

Step 1 — Open the Marketplace​

In the organization navigation (the top-level one, not a site's), choose Marketplace.

It's at the organization level on purpose. What you install is available to every site you choose, so it isn't a per-site setting, and you don't repeat the work for each site you run — the thing agencies and multi-site teams notice first.

Its own navigation panel lists:

  • Browse All — the catalogue.
  • Installed — what you already have, with upgrade and uninstall.
  • and, once you publish, the seller sections: Upload / Publish, Publisher Profile, Listings, Payouts, Sales.
Marketplace is the shop; Plugins is the switch

There is a separate Plugins section in the same organization navigation. That is where things get turned on and off — including Aglyn's own built-in plugins. Marketplace installs, Plugins toggles. If you are looking for a switch and can't find one, you're in the wrong section. More on the split.

Step 2 — Find something​

Browse All is a grid of listing cards you can search, filter and sort. Cards are a catalogue only — clicking one takes you to its detail page, which is the only place an install can happen. You cannot install by accident from the grid.

Two things on a card are worth reading before you click into one:

  • The price chip. Every card has one. A paid listing shows $29; a free one shows the word Free, rather than leaving the corner empty for you to interpret.
  • The stars, and the number beside them. 4.8 (12) is twelve people's opinion; 5.0 (1) is one person's. A listing nobody has rated says Not yet rated instead of showing no stars.

On the detail page, read three things before anything else:

  1. The What's included box. Aglyn writes it from the listing itself, not the publisher, so it is the one description that cannot oversell. Its first row names what the install produces — a sandboxed plugin, an editable component, screens you rework in Besigner, a theme, or a new empty dataset with its fields already defined for a dataset schema, which is the reminder that records never travel: you get the shape, not somebody's data. The rows after it cover where it lands (step 4), review, licence and updates. See What's included for every row it can produce.
  2. The badges. They make two different claims, and it's worth knowing which is which — see what the badges mean.
  3. The price. The header repeats the card's chip — $29, or Free — and the button spells out what pressing it does: a paid listing reads Buy for $29 rather than Install. Buying is one payment; the listing's updates are included in it.

Step 3 — Read the reviews, and know who can leave one​

Ratings on a listing come only from people with a verified email whose organization actually installed it. Comments are open to any signed-in user. So a listing's star rating is a claim by users, and its comment thread is a claim by anyone — weight them differently.

Step 4 — Choose which sites get it​

This is the step to read.

On the detail page you'll find an Install to dropdown with two options:

OptionWhat it means
All sitesEverything in the organization. For a plugin, that includes sites you add later.
Selected sitesOnly the sites you tick. A Sites checklist appears underneath — tick at least one.

"All sites" does not mean the same thing for every kind of listing, and that is the whole reason this step exists:

  • Plugins and dataset schemas install organization-wide. A site you create next month gets them too.
  • Components, templates, layouts, themes and email templates are site-scoped. "All sites" copies them onto every site you have right now; a site you add later will not have them.

You will have seen this fact once already, in the What's included box further up the page — Installs org-wide, covering sites you add later, or Installs per site — new sites are not covered automatically. The helper text under the Install to dropdown is the same fact with your own numbers in it: for the site-scoped case it reads "Installs to all 4 sites. New sites won't get it automatically." Two wordings, one behaviour — if they ever seem to disagree, the helper text is the one counting your actual sites.

"Selected sites" only appears when there's a choice to make, so on a one-site organization you won't see it.

Every site here is a live site

There is no staging site in Aglyn. Whatever you install is reachable by real visitors as soon as it's on a site. If you want to try something cautiously, install it to one site — ideally the quietest one — rather than to all of them.

Step 5 — Install it​

Press Install (or Buy for $…). A confirmation dialog names the listing, its type, its version, and — in bold — exactly where it's going:

Install Bookings Pro (plugin, v2.1). This will be installed to all sites.

Read that bold phrase. It is the last chance to catch a mis-set target, and it is why the dialog exists.

Choose Install. That's it.

Two things happen that are worth knowing:

  • The install is version-pinned. You have v2.1 and you keep v2.1 until you deliberately upgrade. A publisher shipping v2.2 tomorrow does not change your sites overnight.
  • A plugin is enabled for the workspace automatically. You don't have to go and switch it on after installing.

Step 6 — Use it​

Where it shows up depends on what you installed:

  • Plugins add a named group to the Besigner's elements drawer, and often a page in the console navigation.
  • Components, layouts and templates appear in the drawer and in your site's templates library, badged Marketplace with the version they came from.
  • Themes apply to the site you chose.
  • Dataset schemas appear as a new, empty dataset under Data.
  • Email templates arrive as a draft email you can edit before sending.

Step 7 — Turn it off, or take it back off​

Three different actions, often confused:

You want toWhereWhat happens
Stop it running, keep itPlugins → its switchOff everywhere in the workspace. Flip it back any time.
Remove it from your sitesMarketplace → Installed → Uninstall, or Uninstall org-wide on an org-wide install. The listing's own detail page carries the same button.The pin and the switchboard entry go.
Update itMarketplace → Installed, or the detail page's Update to v2.2 buttonYou move to the new version, deliberately.

Uninstalling never deletes the data a plugin created. Reinstall it and it picks up where it left off. That is deliberate — an accidental uninstall shouldn't cost you a year of bookings — but it also means uninstalling is not how you erase data. For that, delete the data itself.

Design copied onto a site behaves differently, and the difference matters: a component or template you installed and then edited is now your copy. Uninstalling the listing doesn't reach into your screens and remove it, and updating shows you field by field what the publisher's new version would overwrite before it touches your edits.

What to do next​