How-to
Article MarkdownReport an error

How to Log In as a User?

When you need to verify what an operator sees in the system without asking for their password, an administrator or authorized supervisor can log in as the selected user and work in the interface with that user's permissions and settings.


When You'll Need This

  • An operator reports they cannot see a required module, filter, or button — you need to verify this firsthand.
  • After changing a role or permissions, you need to confirm the operator received the expected access.
  • A supervisor is preparing instructions for the team and wants to follow the same path as the operator.

What's Important to Know

  • Login as user (button) — an action in the user card that replaces your current session with the selected user's session.
  • Login as user (permission) — a checkbox in Additional settings of the Operator panel when editing a role; it allows this action without root access.
  • After logging in, you work as the selected user: you see the same modules, menus, and restrictions they do.

Before You Start


Step-by-Step Instructions

1. Open the User Card

  1. Go to Settings via Menu -> Settings.
  2. In the side menu, expand Users and open Users.
  3. Find the required user in the table and open them for editing (click the row or the edit button).

2. Log In as User

  1. In the edit form, find the Login as user button.
  2. Hover — a tooltip appears: "Log in as this user. Your current session will be replaced."
  3. Click Login as user — a warning appears: "Are you sure you want to log in as this user? Your current session will be replaced."
  4. Click Login as user again to confirm, or Cancel if you changed your mind.
  5. After a successful login, the page reloads — you land in the main interface with the selected user's permissions.

What Happens After

  • Your previous session is replaced with the selected user's session.
  • All actions in the system are performed as that user (with their permissions and settings).
  • To return to your own account, log out and sign in with your credentials.

How to Verify It Worked

  • After reload, check the user name in the interface — it should show the selected operator.
  • Open the modules in question (for example, Operator Line) and confirm menus and buttons match that user's permissions.

Via MCP

An external AI assistant (an MCP client such as Cursor) can act as another user without a browser — with the impersonate_user tool. ConnectiveOne 6.0.2 or newer is required.

Who can: an MCP key of a role with the Login as user permission enabled, or root. How to get a key — see How to get an MCP token for an instance.

How it works:

  1. The AI assistant calls impersonate_user with the user ID (user_id).
  2. The server checks the permission and the restrictions (the same as for the button, see below).
  3. The assistant receives a token of the selected user valid for 15 minutes for ConnectiveOne API requests on their behalf.

What's important to know:

  • The real user is not logged out, and their status does not change.
  • The token cannot be refreshed or exchanged for a longer one.
  • The tool appears automatically in MCP keys of every role with the Login as user permission. If the permission was enabled earlier for the button, the tool appears after the update with no extra action. Turn the permission off in the role if MCP access on behalf of others is not needed.
  • The built-in instance AI agent does not have this tool.
  • An MCP login is visible in the action log: both on the account that logged in and on the account it logged in as (marked with the MCP key).

⚠️ Risk. The token gives the selected user's full access, including admin rights. Only root, system and technical accounts are excluded. 15 minutes do not limit what can be changed in that time: creating users, changing passwords. Never paste the token into chat, notes, tickets or logs.


Limitations

  • The Login as user button does not appear for inactive users, for yourself, or for root users (unless you are root).
  • You cannot log in as a user with the root role (unless your own account is root) or as system and technical accounts (for example, technical users of MCP keys) — neither with the button nor via MCP; the system returns an error.
  • In the current version there is no indicator that you are viewing the system as another user, and no dedicated exit button for this mode — only the standard log out.

Using your own AI agent?Install the open skill so your AI agent can work with current official ConnectiveOne documentation.Get the skillNeed support?Couldn’t find the answer or need help from the ConnectiveOne team? Create a request in Client Portal.Create a request