> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/management/users.md). # Users **Category:** Management **Version:** 1.0 **Last Updated:** July 9, 2026 **Author:** Any2Info *** ### Description The **Users** page is the central location for managing and monitoring platform users. Administrators and users with the **User management** permission can create new users, update user information, manage authentication settings, assign roles, configure managed users, inspect user authorizations, and review active user sessions. The page provides an overview of all users registered within the platform. *** ### Users Overview The overview displays all users together with their most important account and authentication information. #### Search The search field supports searching by: * User ID * Username * SSO username * First name * Infix * Last name * Full name (Firstname Lastname) * Full name including infix (Firstname Infix Lastname) * Email address * Phone number > **Note** The overview cannot be sorted or filtered. Only searching is supported. *** ### Columns | Column | Description | | -------------- | ---------------------------------------------------------------------------------------------------------------- | | Id | Unique identifier of the user. | | Admin | Indicates whether the user has platform administrator rights. | | Username | Username used to log into the platform. | | SSO username | External username used for Microsoft, Google or Apple authentication when it differs from the platform username. | | Firstname | User's first name. | | Infix | Optional name infix. | | Lastname | User's last name. | | Email | Registered email address. | | Phone | Optional phone number. | | Biometrics | Indicates whether biometric verification is required in the mobile application. | | MFA | Indicates whether Multi-Factor Authentication is enabled. | | Disable MFA | Indicates whether the user is allowed to disable MFA themselves. | | Disabled | Indicates whether the account has been disabled. | | Locked | Indicates whether the account is temporarily locked after multiple failed login attempts. | | Add collection | Indicates whether the user is allowed to create new collections. | *** ### Creating a User Select **New user** to create a new platform user. Users can also be created automatically through a **Create User** node within a Dataflow. *** ### Context Menu Right-clicking a user opens the context menu. Available actions include: * Edit * Edit Password * Delete * Variables * Configure managed users * Associations * Tokens If a user's account is locked, an additional **Unlock account** option becomes available. Accounts are automatically locked for **1 hour** after **5 failed login attempts**. *** ### Edit User The **Edit user** dialog contains four tabs. #### Personal Manage the user's personal information. | Setting | Required | Description | | --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | Profile picture | No | Displays the user's profile picture. Users can upload their own profile picture through the Web App or Mobile App. Administrators can remove the picture. | | Username | Yes | Unique username used for logging into the platform. Can be modified provided the new username is unique. | | Firstname | Yes | User's first name. | | Infix | No | Optional name infix. | | Lastname | Yes | User's last name. | | Email | Yes | User's email address. | *** ### Business Optional business information. | Setting | Required | Description | | ---------- | -------- | ----------------------------------- | | Phone | No | Contact phone number. | | Company | No | Company name. | | Department | No | Department within the organization. | | Job | No | Job title or role. | *** ### Platform Settings Platform-specific account settings. | Setting | Description | | --------------------------- | ----------------------------------------------------------------------------------------------- | | Admin rights | Grants platform administrator permissions. | | Multi factor authentication | Requires Multi-Factor Authentication for this user. | | User disabled | Disables the account while preserving all user information. | | Biometrics check in app | Requires biometric verification when using the mobile application. | | Create collections | Allows the user to create new collections. | | Allowed to disable MFA | Allows the user to disable MFA themselves. When disabled, administrators can enforce MFA usage. | *** ### Authorisation Configure the user's platform authorization. | Setting | Description | | ------------ | ---------------------------------------------------------------------------------------- | | SSO username | External Microsoft, Google or Apple username when it differs from the platform username. | | Add role | Assign one or more roles to the user. | | Roles | Displays all assigned roles. Roles can be removed using the delete icon. | A user can be assigned multiple roles simultaneously. *** ### Edit Password Allows an administrator to change the user's password. This is typically used when a user has forgotten their password or when an administrator needs to reset credentials. *** ### Delete Deletes the selected user from the platform. *** ### Variables Opens the user-specific Variables editor. Variables can be used to personalize application behavior for individual users. For more information, see the **Variables** documentation. *** ### Configure Managed Users Managed Users allows administrators to configure impersonation. This feature is commonly used when an employee is temporarily unavailable, allowing another employee to take over their account without sharing passwords. Both **individual users** and **groups** can be assigned. Once configured: * Access becomes available immediately. * No password sharing is required. * Users can switch accounts using the **Run as user** option available in both the Web App and Mobile App. * The **Run as user** option is only visible when the user has permission to impersonate at least one other user. *** ### Associations The **Associations** window provides a read-only overview of how a user is authorized within each collection. The window displays: * Collections the user has access to * Roles assigned within each collection * Effective permissions resulting from those roles Authorization information is grouped into: * Modules * Dashboards * Forms * Agents * Dataclips * Dataflows * MCPs Expanding a permission shows which assigned role granted that permission. This screen is intended for inspection and troubleshooting and cannot be used to modify permissions. *** ### Tokens The **Tokens** window provides a read-only overview of the user's active sessions. For each active session the following information is shown when available: * Login date and time * Client type * Browser or application * Operating system * Version information Administrators can use this information for auditing and troubleshooting active logins. > **Note** Active sessions cannot be revoked by administrators. Users can manage and revoke their own active sessions from the Web App or Mobile App. *** ### Permissions Access to the **Users** page requires one of the following: * Platform administrator rights * User Management permission *** ### Tips & Best Practices * Disable user accounts instead of deleting them when an employee leaves the organization. * Enforce Multi-Factor Authentication by disabling the **Allowed to disable MFA** option. * Use **Configure managed users** instead of sharing passwords when temporary account access is required. * Review the **Associations** window when troubleshooting authorization issues. * Review active sessions using the **Tokens** window when investigating unexpected logins. *** ### Typical Workflow 1. Create a new user. 2. Enter the user's personal information. 3. (Optional) Enter business information. 4. Configure platform settings. 5. Assign one or more authorization roles. 6. (Optional) Configure managed users. 7. The user signs in to the platform. 8. Use the **Associations** and **Tokens** windows later for auditing and troubleshooting. *** ### Changelog | Version | Date | Change | | ------- | ------------ | ------------------------------------ | | 1.0 | July 9, 2026 | Initial documentation version added. | --- # 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://academy.any2info.com/any2info-academy/no-code-platform/management/users.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.