Managing packages

A package bundles everything a person should receive when they join: AI credits, AI agent access, a company placement, a subscription, or any combination. You build it once on the Audience → Packages page and then reuse it, so onboarding a hundred people is the same amount of work as onboarding one.

A package on its own does nothing. It reaches people only when something grants it: a promotion, a company, a team, an invitation, or the tenant default.

What a package can grant

Each thing a package does is an action. A package holds at most one action of each type, and you add them on the package's detail page.

• Start subscription. Opens a time-limited subscription so the person can watch lessons and courses. You set the length in days. See Managing subscriptions.
• Add AI credits. Tops up the balance a member starts with. Choose Limited and enter a number, or Unlimited. Limited grants are drawn from your tenant's credit pool, the same pool the Dashboard balance tracks.
• Add to company. Places the person in a company, and optionally on a specific team inside it. Leave the role blank and they land at the company root.
• Grant AI agent access. Gives access to specific AI agents, each optionally marked featured. This one appears on Fuel tenants only. Everywhere else all agents are already public, so granting access would change nothing.

Every action has an Enabled switch. Turn one off to stop it applying without losing how you configured it.

Create a package

1. Go to Audience → Packages and click New package.
2. Setup. Name the package and describe it. The name is what you'll pick from later, so make it specific: "Enterprise onboarding" beats "Package 2".
3. Actions. Choose what it grants and fill in each one's configuration.
4. Promotion. Optionally give the package a shareable signup link right away. Leave the name blank to skip this and add promotions later.
5. Review. Check the summary, then create.

You land on the package's detail page, where you can add more actions, attach owners, and see its promotions.

How a package reaches people

Five things can hand out a package. Whichever one applies to a person is the package they get.

• A promotion. Anyone who signs up through the link, or enters the code, receives it. See Managing promotions.
• A company. Everyone who signs up into that company receives it.
• A team. Narrower than a company: only that team's signups.
• An invitation. Attached to one specific invite, so only that person receives it.
• The tenant default. The catch-all for every signup that none of the above covers.

Attach a package to a company, team, or invitation

1. Open the package and find Attached owners.
2. Click Attach owner.
3. Pick a company, then optionally narrow to a team inside it. Or switch to an invitation and pick the invite.
4. Click Attach.

To undo it, click the unlink icon on the row. Future signups stop receiving the package. Grants already applied stay put.

Set the tenant default

Open the menu on any package row and choose Set as default. Only one package can be the default at a time, so setting a new one clears the old.

The default is a good place for the baseline every new member should get, like a starter credit balance or a trial subscription. Anything more specific overrides it.

Edit or delete a package

Use the menu on a package row, or the menu on its detail page, to rename or delete it.

Deleting asks you to detach the package from its owners first. Grants that already went out are kept in the activity ledger either way, so deleting a package never claws anything back from people who already received it.

Activity

Activity is the ledger of every grant applied to every user: signups through a promotion, company and team attachments, invitations, the tenant default, and manual redemptions. Reach it from View activity on any package, or from the Packages page.

Each row shows the user, the action and the package it came from, the scope that triggered it, the status, and when it happened. Filter by user, by package, or both.

Status is one of three things:

• succeeded. The grant applied.
• skipped. The grant did not apply because it did not need to, and the Reason column says why.
• failed. Something went wrong. Use the retry icon on the row to run it again.

Tips

• Check Activity after a launch. A failed row means someone did not get what you promised them, and it will not fix itself.
• Set a default package before you start inviting people. Without one, a signup that no promotion or company covers receives nothing at all.
• Give a package one job. Two narrow packages are easier to reason about than one that grants everything to everyone.