--- title: "Assigning roles for local user accounts" slug: "assigning-roles-for-local-user-accounts-1" tags: ["File Protect (FX)", "Malware Analysis (AX)", "IAM", "Email Security - Cloud", "Network Security (NX)", "Email Security — Server", "Central Management System", "Helix Enterprise", "Endpoint Security (HX)", "Product Usage", "Install and Get Started", "Helix", "Intelligent Virtual Execution "] updated: 2026-08-20T07:29:05Z published: 2026-09-01T19:03:25Z canonical: "docs.trellix.com/assigning-roles-for-local-user-accounts-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Assigning roles for local user accounts For every role, there is a corresponding system account by the same name that has the role. System accounts cannot be deleted or modified, with the exception of being locked out so they cannot be used to log in. By default, each new user is granted the monitor role. An administrator can change the role or give a user no role; a user with no role cannot log in to the appliance. If a role is changed while the affected user is logged in, the user will be forcibly logged out. When the user logs in again, the capabilities provided by the new role are available to the user. Users in all roles can change their passwords and perform other account management functions. For details, see [Managing your own account](/docs/managing-your-own-account). For details about the capabilities associated with each role, see [Capabilities of local roles on CM Series, EX Series, and NX Series appliances](/docs/capabilities-of-local-roles). :