Review permissions and install a package

Installing is a short, guided flow. You see what a package will access before anything is added, and you must confirm.

Start

1. Open a package and choose Install. You need to be signed in with your PGBHub account.
2. In 1. Where should it go?, choose a target:
   • Studio project: build and edit it in PGB Studio.
   • Agents: run it from PGB Agents.
   • Console project: add it to one of your hosted projects.
   • Business workspace: add it to a PGB Business workspace you manage.
3. For a console project or workspace, paste its ID (you need permission to manage it). Studio and Agents have an optional ID; leave it empty to use your default.
4. Choose Review what will be installed.

Agents and templates default to the Agents and Studio project targets.

Review

2. Review shows:

• Any warnings.
• Also installed first, a list of packages this one depends on.
• What it will be able to access: each permission in plain language, most risky first, with a risk pill. Examples: Read your business email (medium), Write email drafts (low, "nothing is sent without you"), Send email for you (high), Contact outside services (high), Change your project data (high).
• Settings: fields the publisher asks you to fill in, for instance a mailbox address or a choice of tone. Required ones are marked with an asterisk.
• A note if it needs secrets. You add secrets yourself afterwards in your project's secret settings, never in this form.

Confirm

Tick the box that says you have reviewed what the package, and any packages it brings, can access. If anything is high risk, the text says so. Then choose Install. Back returns to step 1.

After installing

You see " is installed" and Next steps, which depend on the target. For a secret it needs, add it in your project. Then use My installs to see it. See My installs.

For an agent or template, the most reliable next step is to open PGB Agents (New agent, From the marketplace, Use this agent) or PGB Studio (Start from a template) and start it from there. See Create an agent and Start a project from a template.

Good to know

• Settings you enter must be declared by the package. Secrets are refused in settings.
• Installing the same package again upgrades or reconfigures it.
• Agents can also use the Marketplace tools themselves, but installing always needs your approval.