> For the complete documentation index, see [llms.txt](https://zakariaes-organization.gitbook.io/saascore-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zakariaes-organization.gitbook.io/saascore-docs/authentication-flow/for-affiliates.md).

# For Affiliates

If you understand the authentication flow for clients, this will be straightforward because it’s essentially identical.

It's like setting up a free account for a client (as described in Scenario 1) but with a different role, "AFFILIATE," which is passed from the sign-up page to the backend.

**Process**:

1. **Sign-Up**: On the sign-up page, select the option to sign up as an affiliate.
2. **Backend Handling**:

   * When the account creation request is sent to the backend, the role `AFFILIATE` is assigned during the `setupUserAccount()` function.

   ```jsx
   await prisma.user.update({
       where: { id: userId },
       data: {
           roles: {
               set: ["AFFILIATE"],
           },
       },
   });

   handleAfterSignupTasks({
       email,
       name,
       userId,
       isAffiliate,
   });
   ```

For further queries or assistance, refer to the code comments or contact our support team.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://zakariaes-organization.gitbook.io/saascore-docs/authentication-flow/for-affiliates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.