> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/supplyd-erp/settings/users/users-overview.md).
# Users Overview
Supply'd allows you to add as many users as you require to the platform. Each user can be granted access to specific sections of the site depending on your requirements for them.
The **Users** section in Supply’d allows you to manage everyone who has access to your account. From here, you can add individual Users, create User Groups, and configure permissions, locations, departments and restrictions. This helps ensure each team member has access appropriate to their role while keeping your account secure.
This document explains what **users** and **User Groups** are and guides you through the **Users** page, including how to view user details and review their account settings and permissions.
* [#what-is-a-user](#what-is-a-user "mention")
* [#what-is-a-user-group](#what-is-a-user-group "mention")
* [#the-users-page](#the-users-page "mention")
* [#user-details](#user-details "mention")
***
## What is a User?
A **User** is an individual team member with their own email address and Supply’d login. Each User can be assigned specific permissions, locations, departments and restrictions based on their responsibilities.
Individual User accounts provide team members with access to the tools and information required for their role while allowing their activity to be tracked separately.
{% hint style="success" %}
👉 For details on adding and managing Users, see the [Adding Users](/supplyd-erp/settings/users/adding-users.md) documents.
{% endhint %}
***
## What is a User Group?
A **User Group** allows multiple team members to share the same Supply’d login. When a group member logs in, they enter their unique PIN so Supply’d can identify and track their individual activity.
User Groups are useful for teams that access Supply’d through a shared account or device but still need visibility and accountability for the actions performed by each person.
{% hint style="success" %}
👉 See the [User Groups](/supplyd-erp/settings/users/user-groups.md) documents for information on adding and managing User groups.
{% endhint %}
***
## The Users Page
The **Users** page provides a central place to view and manage everyone who has access to your Supply’d account. From here, you can add individual Users, create User Groups, and manage each user’s access, permissions and restrictions.
To view the **Users** page, click on your name or company logo in the top right, then select **Users**.
{% hint style="success" %}
The **Users** page can also be accessed by going to **Settings**, scrolling down, and selecting **Users** from the menu.
{% endhint %}
The **Users** page will open listing all the **Users** that have access to your account.
{% hint style="success" %}
Different **User Types** give team members access to the features and workflows relevant to their responsibilities, making Supply’d easier to use while improving security, accountability and operational control. Each user’s **User Type** appears as a colour-coded tag beside their name, making their role easy to identify from the **Users** list.\
* 
- Has full access to the Supply’d account, including business settings, billing, users and all available features.
* 
- A general user whose access can be configured according to their role and responsibilities.
* 
- A **User Group** allows multiple people to use a shared login, with each person entering their own unique PIN. This lets Supply’d identify each sub-user and track their activity within the shared account.
* 
- Team members involved in manufacturing or preparation, providing access to relevant production features and workflows.
* 
- Sales team members who manage customer relationships, place or review orders and perform other sales-related activities.
* 
- Drivers completing deliveries, allowing them to view assigned delivery runs, navigate to customers and update delivery statuses.
{% endhint %}
***
## User Details
Select a user to open their details.
The user’s details page provides an overview of their account, contact information and access settings, including:
* **Name and Account Type** - The user’s name and a label identifying their account type, such as **Sales Rep**.
* **Email and Mobile** - The user’s contact details.
* **Timezone** - The timezone configured for the user.
* **2FA Enabled** - Whether two-factor authentication is enabled.
* **Last Login** - The date and time the user last logged in.
* **Order Locations** - The locations the user can place orders for.
* **Order Approval** - Whether the user’s orders require approval.
* **Hourly Rate** - The hourly rate setting applied to the user.
* **Visible To** - Whether the user appears as a contact for connected suppliers or customers.
* **Notifications** - The notifications the user is configured to receive.
* **Access** - The features and information the user can access, including any restrictions.
The three-dot menu in the top-right corner provides additional options for managing the user.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.supplyd.co/supplyd-erp/settings/users/users-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
