# Internal User Accounts ### Overview Internal User Accounts allow warehouses to scale teams freely as operations grow. Operators, managers, and supervisors can each have their own login, making it easier to track individual activity and maintain accountability across the system. Language preferences ensure the platform remains accessible to multilingual teams, reducing training friction and supporting clear communication on the floor. ### How It Works New accounts are created through the Admin section of the platform. A manager enters the user’s name, email, and preferred language, then chooses whether the account will be created as an Admin or a Merchant. Once created, the account becomes active immediately, with all actions tied to that user for full accountability. For Admin accounts, permissions must be configured to define which WMS capabilities they can access — from inventory controls to reporting tools. This ensures each internal user has the level of visibility and control appropriate to their role. In 3PL environments, the “Create Admin” option is available to set up operations accounts across multiple client warehouses. In single-brand WMS deployments, this option is hidden to keep the setup simple, since multi-client functionality is not required. {% embed url="" %} Creating Internal User Accounts — assigning Admin or Merchant roles for immediate access and full accountability. {% endembed %} ### Why It Matters * Scale operations freely by creating accounts as your team grows, without bottlenecks or shared logins. * Strengthen accountability by tying every action in the WMS to a specific user, making it clear who did what and when. * Reduce training friction with language preferences that make the system accessible to multilingual teams. * Adapt easily to different warehouse environments — supporting multi-client 3PL operations while keeping single-brand WMS setups simple. ### Best Practice Regularly audit internal accounts to disable inactive users and remove access for staff who no longer require it. This keeps the environment secure, reduces clutter, and ensures only the right people are active in the system. --- # Agent Instructions: 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: ``` GET https://docs.getlogentic.com/workflows/system-admin-and-settings/internal-user-accounts.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.