diff --git a/content/concepts/users-and-authentication/referral-links/console-referral-link-example.png b/content/concepts/users-and-authentication/referral-links/console-referral-link-example.png
new file mode 100644
index 0000000..a3b2ae1
Binary files /dev/null and b/content/concepts/users-and-authentication/referral-links/console-referral-link-example.png differ
diff --git a/content/concepts/users-and-authentication/referral-links/index.mdx b/content/concepts/users-and-authentication/referral-links/index.mdx
new file mode 100644
index 0000000..4156e3d
--- /dev/null
+++ b/content/concepts/users-and-authentication/referral-links/index.mdx
@@ -0,0 +1,87 @@
+---
+title: Referral links in Sharetribe
+sidebarTitle: Referral links
+description:
+ This article explains how referral links work in Sharetribe, including
+ how referral parameters are captured, persisted as referral data, and
+ saved to user data on sign-up.
+---
+
+import { Callout } from 'nextra/components';
+
+# Referral links in Sharetribe
+
+Referral links allow operators to track how new users arrive at the
+marketplace. When a user follows a referral link, the referral
+parameters in the URL are validated against the referral sources
+configured for each user type in Console. If the user then signs up
+before the expiry window, the referral data is saved to their private
+data.
+
+## Configuring referrals in Console
+
+Referral sources are configured per user type in Console, so a referral
+link is only valid for users who match the expected user type on
+sign-up.
+
+
+
+For more information on setting up referrals, refer to the
+[Help Center article](). {/* TODO: Add Help Center article link */}
+
+## How referral links work
+
+Referral data is captured from the URL on any page load, meaning any
+page on the marketplace can serve as an entry point for a referral link.
+In pages where the URL directly impacts API query parameters - for
+example the search page - the referral link is filtered out of the
+params before the query is made.
+
+A referral link uses the URL parameter name defined in Console combined
+with a referral code. For example, a referral link for a cycling club
+partnership might look like this:
+
+```
+/signup?clubReferral=referral-code
+```
+
+
+ If your custom search code passes URL parameters directly to API
+ queries - for example, by spreading `location.search` params into a
+ listings query - referral link parameters may be unintentionally
+ included. Filter them out before making API calls. See
+ [SearchPage.duck.js](https://github.com/sharetribe/web-template/blob/main/src/containers/SearchPage/SearchPage.duck.js)
+ for an example of how the template handles this.
+
+
+### Persisting referral data
+
+When referral parameters are found in the URL, they are saved to local
+storage as referral data. The referral data persists for 90 days, so a
+user can follow a referral link and sign up at a later point within that
+window and still have the referral captured.
+
+### Validation and sign-up
+
+When a user signs up, the referral data stored in local storage is
+validated against the referral sources defined for each user type in
+Console. The referral sources for a user type are structured as follows:
+
+```json
+{
+ "userType": "seller",
+ "referralSources": [
+ {
+ "label": "Cycling club partnership",
+ "parameter": "clubReferral"
+ }
+ ]
+}
+```
+
+If the referral data is valid and the user matches the expected user
+type, the referral data is saved to the user's private data.
+
+If the referral data is invalid, or the user's type does not match the
+referral source, sign-up proceeds normally and no referral data is
+saved.
diff --git a/content/template/availability/availability-management/index.mdx b/content/template/availability/availability-management/index.mdx
index fe3b3d3..3ed3f85 100644
--- a/content/template/availability/availability-management/index.mdx
+++ b/content/template/availability/availability-management/index.mdx
@@ -40,7 +40,7 @@ be set to `time-full` or `time-partial`. Queries using this
By default, the template will display the first 24 results when using
the date filter (and as pagination is not supported, the results will be
limited to 24). This value can be modified in
-[SearchPage.duck.js file](https://github.com/sharetribe/web-template/blob/main/src/containers/SearchPage/SearchPage.duck.js#L22),
+[SearchPage.duck.js file](https://github.com/sharetribe/web-template/blob/main/src/containers/SearchPage/SearchPage.duck.js#L23),
so you can allow displaying up to a 100 results.
@@ -99,7 +99,7 @@ availability on certain dates. The date search cannot be restricted to
specific time zones. This means that to cover listings from all possible
time zones, the template prolongs the start and end times before sending
them to the Sharetribe API. See the relevant code
-[in SearchPage.duck.js](https://github.com/sharetribe/web-template/blob/main/src/containers/SearchPage/SearchPage.duck.js#L180-L181).
+[in SearchPage.duck.js](https://github.com/sharetribe/web-template/blob/main/src/containers/SearchPage/SearchPage.duck.js#L181-L182).
To be exact, the start time is moved 14 hours earlier, and the end time
is moved 12 hours later. This means that the availability search results
diff --git a/content/tutorial/use-protected-data-in-emails/index.mdx b/content/tutorial/use-protected-data-in-emails/index.mdx
index c76a2b7..0f14f1b 100644
--- a/content/tutorial/use-protected-data-in-emails/index.mdx
+++ b/content/tutorial/use-protected-data-in-emails/index.mdx
@@ -136,6 +136,12 @@ This happens in **_signup_** function at _auth.duck.js_.
└── auth.duck.js
```
+
+ The signup function also handles saving a referral ID to the user's
+ private data when a user signs up via a referral link. This is
+ separate from, and unrelated to, form fields mentioned above.
+
+
## Reveal protected data
There are a couple of ways to reveal the phone number to the other party