> For the complete documentation index, see [llms.txt](https://help.iwantchips.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.iwantchips.com/brands/overvew/authentication.md).
# Authentication
#### **Overview**
The **Authentication Feature** is a critical component of the Chips Rewards Loyalty Platform, ensuring secure and personalized access for both consumers and brand partners. This feature provides robust mechanisms for verifying the identities of users, safeguarding their data, and managing access to the platform's features and resources.
#### **Key Components**
1. **User Registration**
2. **User Login**
3. **Password Management**
4. **Session Management**
5. **Role-Based Access Control (RBAC)**
#### **1. User Registration**
New users can create an account on the Chips Rewards Loyalty Platform using a simple registration process. This process requires users to provide essential details such as their email address and a secure password.
**Steps:**
1. **Navigate to the Registration Page**: Click the **Sign Up** button on the homepage.
2. **Enter Information**: Fill in the registration form with your email and password.
3. **Verify Email**: Check your email for a verification link. Click the link to confirm your account.
4. **Complete Profile**: Optionally, complete additional profile details for a personalized experience.
#### **2. User Login**
Registered users can access their accounts by logging in with their email and password. The login process ensures secure entry and personalized access to the platform.
**Steps:**
1. **Navigate to the Login Page**: Click the **Log In** button on the homepage.
2. **Enter Credentials**: Input your registered email and password.
3. **Log In**: Click **Log In** to access your account. Successful login redirects you to your dashboard.
#### **3. Password Management**
Users can manage their passwords securely, including changing passwords and resetting forgotten passwords through email verification.
**Steps:**
1. **Change Password**: Go to **Account Settings** > **Change Password**. Enter the new password, and confirm the new password.
2. **Forgot Password**: Click **Forgot Password** on the login page. Enter your registered email to receive a password reset link.
3. **Reset Password**: Follow the link from the email to create a new password.
#### **4. Session Management**
Session management ensures that user sessions are secure and inactive sessions are terminated automatically after a period of inactivity.
**Features:**
* **Automatic Logout**: Users are logged out after a set period of inactivity to prevent unauthorized access.
* **Session Overview**: Users can view active sessions in their account settings and terminate any suspicious or unnecessary sessions.
#### **5. Role-Based Access Control (RBAC)**
RBAC allows the platform to restrict access based on user roles, ensuring that each user only has access to features and data relevant to their role (e.g., consumers, brand managers, stores, admin).
**Roles:**
* **Consumers**: Access to personal dashboard, rewards tracking, and redemption.
* **Brand Managers**: Access to brand-specific analytics, campaign creation, and reward management.
* **Stores:**
* **Admin**: Full access to all platform features and user management.
Brands, Stores and Amdin role groups have other 3 Roles with their corresponding permissions:
* Owner
* Manager
* User
* Custom
Learn more about the Brand Roles and Permissions [here](https://iwantchips.atlassian.net/wiki/spaces/SD/pages/73400321).
#### **Contact Support**
If you encounter any issues with the authentication process, please contact our support team at .
---
# 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://help.iwantchips.com/brands/overvew/authentication.md?ask=&goal=
```
`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.