> For the complete documentation index, see [llms.txt](https://help.allwage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.allwage.com/fundamentals/users-and-employees.md). # Users & Employees Assign roles and permissions to your user and employees There is a distinct difference between "**users**" and "**employees**," each with specific access rights and functionalities: * **Users:** These are individuals who have login credentials for the online portal. Users can sign in using their email and password to access, manage, and interact with information on the portal. This group primarily includes **administrative roles** and those who need to oversee or update various aspects of the operations from anywhere via the internet. * **Employees:** This group does not have access to the online portal and **cannot** log in to view or manage data. Their interaction with the system is limited to their specific **operational roles**. However, certain employees, such as foremen, may have the capability to log into the Android application to capture information directly in the field. This allows them to input data relevant to their daily tasks and responsibilities while on-site, but they do not have broader portal access for administrative functions. This structure ensures that data access and management are tailored to the roles and responsibilities within the organization, enhancing security and efficiency. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://help.allwage.com/fundamentals/users-and-employees.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 `build a script that syncs our docs to a CMS` 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.