Post purchase outcomes/redeem for web to app and audit log

content/docs/dashboard/dashboard-creating-paywalls/paywall-editor-styling-elements.mdx

@@ -88,7 +88,7 @@ You can add multiple actions to either **After purchase** or **On Abandon**. The
 - **Custom Placement:** Registers a placement, which can present another paywall if your campaign is configured for it.
 - **Set User Attribute:** Sets one or more user attributes.
 - **Update Variable:** Updates a paywall state variable.
-- **Redeem Purchase:** Handles web checkout redemption behavior where available.
+- **Redeem Purchase:** For Web Checkout purchases, sends the completed checkout through a redemption destination, such as the application default, Superwall's redemption page, a direct deep link, or a custom redirect URL.
 
 Before these actions run, Superwall updates transaction state variables for the current paywall. After a successful purchase, `state.didCompleteTransaction` is set to `true` and `products.purchased` points to the purchased product. After an abandoned purchase, `state.didAbandonTransaction` is set to `true` and `products.abandoned` points to the product the user tried to buy. You can use those variables in follow-up actions, conditional content, drawers, or Liquid values.
 
@@ -102,6 +102,41 @@ Before these actions run, Superwall updates transaction state variables for the
   checkout, Superwall uses the application-level redeem purchase behavior instead.
 </Note>
 
+For mobile purchases, use the standard outcome actions above. The following option only appears when the purchase resolves through Web Checkout.
+
+#### Redeem Purchase for web checkout
+
+Post-purchase actions are available for regular mobile paywalls and web checkout paywalls. **Redeem Purchase** is the Web Checkout-specific post-purchase action: it controls the redemption destination after Stripe checkout completes.
+
+Use it when a Web2App or Web Flow checkout needs to override the application-level post-purchase behavior for one paywall. For example, one checkout button can use the application default while another opens Superwall's hosted redemption page, deep links into the app, or redirects to your own success page.
+
+Add it from the web checkout purchase button's **After purchase** section:
+
+1. Select the button that starts checkout.
+2. In **Tap Behavior**, choose **Purchase**.
+3. Under **After purchase**, click **+ Add**.
+4. Choose **Redeem Purchase**.
+5. Select a **Destination**.
+
+<Frame>![Tap Behavior menu showing Redeem Purchase in the After purchase action selector](/images/web_post_purchase_select.jpg)</Frame>
+
+| Destination | What happens |
+| --- | --- |
+| **Use Application Setting** | Uses the app-level [post-purchase behavior](/web-checkout/web-checkout-configuring-stripe-keys-and-settings#post-purchase-behavior). This is the default and is best when every paywall should follow the same Web Checkout behavior. |
+| **Open Redemption Page** | Opens Superwall's hosted redemption page for the completed checkout, even if the application setting is configured to redirect elsewhere. |
+| **Deep Link** | Opens the generated app deep link for the completed checkout directly. If no completed checkout redemption target is available, the action does nothing. |
+| **Custom Redirect** | Redirects to the URL you enter when the checkout produces a single successful redemption code. Superwall appends checkout context, including placement parameters, the app user ID when available, and Stripe purchase identifiers. |
+
+**Custom Redirect** URLs must include a protocol, such as `https://example.com/success`. You can insert paywall variables into the URL from the variable picker. Use this when the next step is your own onboarding, analytics, account creation, or success page rather than Superwall's hosted redemption page.
+
+If Superwall cannot safely use the custom redirect, such as when the checkout has multiple redemption codes, it falls back to the hosted redemption page.
+
+<Note>
+  **Redeem Purchase** only runs when Superwall has a completed Web Checkout redemption
+  target. For non-web-checkout purchases, use the standard **After purchase** actions,
+  such as **Close**, **Navigate Page**, **Open URL**, or **Custom Action**.
+</Note>
+
 **Navigation**
 
 - **Navigate Page:** Moves through a [Flow](/dashboard/dashboard-creating-flows/getting-started). Use this to progress users through multi-page experiences like onboarding.

content/docs/dashboard/dashboard-settings/overview-settings-audit-log.mdx

@@ -0,0 +1,129 @@
+---
+title: "Audit Log"
+description: "Review organization activity in Dashboard v2."
+---
+
+<Note>
+  Audit Log is available in public beta when you enable New Dashboard Experience for
+  the application you are working in.
+</Note>
+
+Use **Audit Log** to review recent organization activity across the Superwall dashboard and V2 API. It shows who made a request, what they did, whether it was allowed or rejected, and the request context Superwall recorded at the time.
+
+Audit Log is organization-wide. It is useful when you need to confirm who changed a resource, investigate a denied API request, or follow activity from one dashboard session. You can find it in the leading sidebar by clicking the app switcher:
+
+<Frame>![Dashboard v2 sidebar with Audit Log in the organization and project switcher](/images/audit_log_nav.jpg)</Frame>
+
+### Before you start
+
+To use Audit Log:
+
+- Enable **New Dashboard Experience** from **Settings > Public Beta**.
+- Use an account role with audit log access.
+
+Owners, Admins, and legacy Users can view the audit log. Editors, Readers, and Analysts do not have audit log access.
+
+Enabling **New Dashboard Experience** makes Dashboard v2 sections available as they roll out. It does not replace every legacy dashboard page or add Audit Log to the legacy sidebar.
+
+<Frame>![Public Beta settings with Dashboard v2 enabled](/images/beta_new_dash.jpg)</Frame>
+
+<Warning>
+  Audit Log is in public beta. The page, filters, and event details may change as Dashboard v2
+  continues to roll out.
+</Warning>
+
+### Open the audit log
+
+To open the full Dashboard v2 shell, go directly to:
+
+```txt
+https://app.superwall.com
+```
+
+If you are signed in, Superwall opens the Dashboard v2 organization picker. After you choose an organization, Dashboard v2 opens the first available app dashboard with the new sidebar.
+
+You can also open a specific app dashboard when you know the organization and application IDs:
+
+```txt
+https://app.superwall.com/{organization_id}/{application_id}/dashboard
+```
+
+To open Audit Log directly:
+
+```txt
+https://app.superwall.com/{organization_id}/audit-log
+```
+
+If you are already in the full Dashboard v2 shell, you can also open the organization and project switcher in the sidebar, then choose **Audit Log**. The legacy dashboard sidebar does not show this item.
+
+Audit Log is attached to the organization, not a single app. If your organization has multiple projects or apps, the page shows activity for the organization you are currently viewing.
+
+<Frame>![Dashboard v2 Audit Log list with filters and event rows](/images/audit_log_demo.jpg)</Frame>
+
+<Note>
+  Audit Log is in public beta. This interface is a work in progress and is subject to change.
+</Note>
+
+### Read the event list
+
+Each row represents one recorded request. The list is newest first and includes:
+
+| Field | What it means |
+| --- | --- |
+| Actor | The user or API key that made the request. |
+| Action | The parsed action, such as viewing, creating, updating, or deleting a resource. |
+| Resource | The resource type and ID when Superwall can resolve one. |
+| Outcome | Whether the request was allowed or rejected. |
+| Time | When the request occurred. |
+
+Rejected requests are marked so you can quickly find permission or authentication failures.
+
+### Filter activity
+
+Use filters to narrow the list:
+
+| Filter | Use it to |
+| --- | --- |
+| Date range | Show the last 24 hours, last 7 days, last 30 days, or a custom range. |
+| Action type | Show all actions, only views, or only changes. |
+| Outcome | Show all requests, allowed requests, or rejected requests. |
+| Actor | Search by actor name, API key name, or numeric user ID. |
+| Advanced filters | Filter by HTTP method, endpoint ID, or failure code. |
+
+Click **Refresh** to load the latest matching events. Use **Next** and **Previous** to move through additional pages when more events are available.
+
+### Review event details
+
+Click an event to open its detail sheet.
+
+<Frame>![Audit Log entry detail sheet showing actor, request context, resource, changes, and developer details](/images/audit_log_trail.jpg)</Frame>
+
+The detail sheet can include:
+
+| Section | What it shows |
+| --- | --- |
+| Who | The acting user or API key, authentication method, and session ID when available. |
+| Where | Device, location, IP address, and User-Agent context when available. |
+| What | The resolved action, resource type, and resource ID. |
+| Changes | Before and after values for supported mutations. |
+| Why it was rejected | Failure stage, failure code, and status code for denied requests. |
+| Developer details | Lower-level request data such as endpoint, method, path, and request ID. |
+
+When a session ID is present, click **View this session** to filter the list to the other recorded actions from that login session.
+
+### What gets recorded
+
+Audit Log records served V2 API requests for the organization. Entries can include dashboard activity and API key activity, depending on how the request was authenticated.
+
+For each entry, Superwall stores the request outcome, the endpoint, the actor, resource details when known, and request context such as IP address and User-Agent. For supported write actions, Superwall can also show a structured before-and-after change list.
+
+<Note>
+  Some older entries or read-only actions may not include every detail section. For example, a read
+  request may not have changes, and older entries may not include device or location context.
+</Note>
+
+### Related
+
+- [Public Beta](/dashboard/dashboard-settings/overview-settings-public-beta)
+- [Team settings](/dashboard/dashboard-settings/overview-settings-team)
+- [Access Controls](/dashboard/dashboard-settings/overview-settings-access-controls)

content/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings.mdx

@@ -45,6 +45,12 @@ When using Redirect mode, you'll need to provide a **Redirect URL** (must start
 
 Learn more about [post-checkout redirecting](/sdk/guides/web-checkout/post-checkout-redirecting).
 
+<Note>
+  This application setting is the default for Web Checkout purchases. A web checkout paywall
+  can override it for a specific purchase button with a **Redeem Purchase** after-purchase
+  action. See [Redeem Purchase for web checkout](/dashboard/dashboard-creating-paywalls/paywall-editor-styling-elements#redeem-purchase-for-web-checkout).
+</Note>
+
 ### Web Paywall Domain 
 
 This is the domain your paywalls will be shown from. This was set when the Stripe app was created, and cannot be changed.

content/shared/web-checkout/post-checkout-redirecting.mdx

@@ -42,6 +42,14 @@ https://yourapp.com/success?
 
 You'll need to implement your own logic to handle the redirect and deep link users into your app.
 
+### Paywall-level overrides
+
+The app-level **Post-Purchase Behavior** setting is the default for checkout links and web checkout paywalls. This is separate from the paywall editor's **Web Checkout Location** setting, which controls where the checkout opens.
+
+For a specific web checkout paywall button, you can override the app-level default by adding a **Redeem Purchase** action under the button's **After purchase** behavior. The action can use the app-level post-purchase behavior, open Superwall's redemption page, deep link directly into your app, or redirect to a custom URL.
+
+See [Redeem Purchase for web checkout](/dashboard/dashboard-creating-paywalls/paywall-editor-styling-elements#redeem-purchase-for-web-checkout) for the dashboard setup.
+
 ---
 
 ## Setting Up Deep Links