Activity feed

Where to find it

Two feeds, each scoped to what you have permission to see:

• Customer activity - your purchases, tokens, subscriptions, and refund activity. If you are an owner or admin of a workspace, team events for that workspace surface here too.
• Vendor activity - events affecting your vendor account, your packages, and your payouts. Visible to customers who have an associated vendor.

Two members of the same workspace will not always see the same rows. Each feed filters by what your account is involved in.

What you see on each row

Each row has three columns:

• When - the date and time the event was recorded.
• Action - a short label naming the event, for example license.granted or token.rotated.
• Details - a short list of context fields relevant to the event, such as the package name, project, amount, or role. Internal identifiers and raw payment payloads are kept off the row.

What appears on the customer feed

• Licences granted, extended, or deactivated against your account.
• Subscription cancellations you scheduled, and any cancellations you later resumed.
• Refund requests you submitted, plus their approval, denial, or cancellation outcome.
• Project tokens you created, rotated, or revoked.
• Licence activations you removed from one of your projects.
• If you are a workspace owner or admin: invites sent, accepted, revoked, extended, or expired; members added, removed, or moved between roles; project guest access granted or removed; the workspace itself being created.

What appears on the vendor feed

• Vendor application submitted, approved, or rejected, and edits to your vendor profile.
• Stripe onboarding completed, payout schedule updates, and auto-suspension events.
• Packages created, activated, deactivated, repriced, or auto-included as hidden dependencies. Admin edits to package metadata show up here too.
• Version ingest succeeded or failed, and archive build succeeded or failed.
• Payouts recorded for your sales, with gross and net amounts.
• Stripe disputes (chargebacks) raised against your sales, as they move through their lifecycle.
• Abuse reports a buyer filed against one of your packages, plus how it was resolved.

Sensitive details

The feed only shows what you need to recognise an event. Card numbers, full Stripe payloads, and internal identifiers are kept off the row. If you need a deeper view (for example for a support conversation), get in touch through our contact form with the date and time of the event you are asking about.

Permanent record

Activity rows cannot be edited or deleted from the website. The feed is the record of what happened and when. If you spot a row that looks wrong, contact support rather than trying to remove it.