Install requests and policy

Install requests and policy

Your organization's owners and admins are its stewards for the Marketplace. They set the install policy, answer install requests, and approve updates that widen what an installed listing can reach. Every change is recorded in the audit trail.

The Requests tab: an install request with who asked, why, and the exact access, and an update that adds a field

Set the install policy

  1. Open Marketplace → Policy.
  2. Choose who may install each kind of listing:
Setting Options What it covers
Listings that only read Anyone can install, A steward approves Read from connectors and post nothing anywhere.
Listings that write A steward approves, Anyone can install Post, create or send anything, inside or outside the company.
Publishers Harmony and verified only, Harmony only Whose listings can be installed here at all.
  1. Choose Save policy.

Cost isn't a setting: runs count against the installer's usage limit, like any Loop. The Stewards card lists the people who answer requests.

The install policy with three settings and the list of stewards

Answer an install request

When someone asks to install a listing your policy holds for approval, it appears under Marketplace → Requests, and the tab shows how many are waiting.

Each request shows:

  • Asked by: who, whether it's their own copy, and the schedule they chose.
  • Why: what they said it would help with.
  • Access: everything it reads (connector, records and only these fields) and writes.
  • How its runs complete in other organizations, what it's Paid from, and whose connections its Data runs on.

Choose Approve for everyone here to approve it for the whole organization, or Decline and say why. They see your reason. Open listing shows the full listing first. Use Show answered too to see past decisions.

Approve an update that widens access

When a new version of an installed listing asks for more (another field, another record, a new write), it appears under Updates that change access, marked New access. The change is shown line by line: what it read before and what it would read now.

  • Approve the new version (the button names it, for example Approve 1.1.0).
  • Stay on the current version: copies here keep running the version you approved.

FAQs

Who are the stewards? Everyone who is an owner or admin of the organization.

Does approving a request install it for everyone? It approves the listing for the organization. For a Loop, each person still installs their own copy; for a tool, it becomes available to everyone.

Where is the decision recorded? In the organization's audit trail, with who decided and when. See Governance and audit.