Skip to content

Act as someone

Act as is for checking access. After you change groups, private features, people properties or who an app is for, act as the person to see what they now see:

  • which features, tables, apps and Saved Agents they find;
  • what an app shows them;
  • what Ronja answers when they ask about a table.

You see Ronja with their role, groups and properties, so what you see is what they get.

  1. In Users & Access, open the person’s Settings page.
  2. Under Act as, click Act as .

Ronja reloads as that person. A dark bar at the top of every page reads Acting as , with the time acting ends, and Leave.

  • Acting lasts at most an hour. When the hour is up, Ronja reloads as you the next time you do something, and says You are no longer acting as . The same happens if you are no longer an Admin, or if the person’s role changes to one you can’t act as. An app you opened while acting keeps working until you leave, or at the latest until the hour is up.
  • Every tab in this browser acts as the person. A tab opened before you started, or one still showing the person after you left in another tab, reloads the next time you do something in it. To change someone’s access, click Leave, make the change, and act as them again.
  • A link to another organization opens a page that says This link is in another organization and offers Leave.
  • Leave reloads Ronja as you. Apps you opened while acting stop working. Work that was already running, such as a chat answer or a workflow, finishes.
  • Signing out also ends acting.

A few things of theirs stay closed while you act as them. These say Not while acting as followed by their name, or don’t appear at all:

  • Their earlier chats, with Ronja or with a Saved Agent. You see only the chats you start while acting. Those chats are theirs and appear in their own chat list. Ronja does not learn from them.
  • Their own policy and personal memory.
  • Approvals that name them as the approver, such as a run’s approval or a change list proposed for them. Reviews any maintainer of a feature may decide, such as its proposals, still work while you act as a maintainer. They show as you acting as them. Where your organization doesn’t allow self-approval, you also can’t decide your own drafts while acting. Nor can you decide a draft of theirs that was open while you acted as them; another Admin can.
  • Their own connections, such as their Google or HubSpot sign-in, in their own private features. Their own Saved Agents, workflows and apps still run with the connections they use.
  • Anything that would let you act as them later. That means creating a token, proposing or approving a change list, approving a command-line sign-in, connecting an AI assistant, signing in to a connector or a mailbox, or deleting their account.
  • Accepting the terms of service and dismissing the welcome screen.
  • Switching to or creating another organization.

Anything you change while acting shows in its Activity as you acting as them, for example Adam as Anna. The Audit log lists it under the person. Starting and leaving are recorded too. AI used while acting counts toward your own limit.