Skip to content
Kibi Connect
Manual Kibi Connect

Support access and login as a person

Updated Reading time: 6 min

On this page

Sometimes it helps to view the platform through the eyes of a specific person, for example, if something looks different for them or isn't working. For this purpose, Kibi Support and your company's system admins can log in with a person's account. This only works with the person's approval, is time-limited, can be ended at any time, and is logged.

At a glance#

For Kibi Support and your company's system admins, the following applies equally:

  • Request open: 72 hours.

  • Approval valid: 24 hours, for one login.

  • Session lasts at most: 24 hours.

  • Works council area: blocked.

The differences:

  • Who requests? Kibi Support employees or people with the System Admin role.

  • Person's approval: Required for Kibi Support, except in cases where it is technically absolutely necessary (see below). For system admins, always required without exception.

  • Where is the request made? Kibi Support requests access in the Kibi Support area; system admins request it in the person's profile via Actions ("...") → Log in as person.

When someone requests access to your account#

If Kibi Support or your administration requests access, you will receive a notification in the bell icon and as a push notification on your devices:

  • "Support requests access": A person from Kibi Support wants to log in.

  • "Your administration requests access": A system admin from your company wants to log in.

You will receive this notification even if you have muted notifications of this type. "Do Not Disturb" and your working hours apply as usual: Outside your working hours, the notification will only appear at the start of your next working hours in the bell icon, without a push notification. "Do Not Disturb" disables all notifications, including this one.

Bell icon with the notification „Support requests access“

How to respond#

Click on the notification in the bell icon. The request will open.

You will see who is requesting, when, and for what reason. The countdown You can still respond shows how long the request remains open.

Choose Approve or Reject.

Request with reason, countdown, and the buttons „Reject“ and „Approve“

The person who made the request will immediately be informed of your response in the platform and via email. If you reject the request, it will then be marked as Rejected, and no one will log in with your account.

Info

With your approval, the person who requested access can log in with your account once within 24 hours. They will then see the platform exactly as you do.

Tipp

If the page says "This request does not exist, or it is not intended for you," the link is not intended for your account. Only the person to whom the request is addressed can respond to it.

Confirming a request as a system admin#

As a system admin, you also respond in this way. However, only Kibi Support can contact you, as another system admin cannot log in with your account. The request will then be called Support Access and will name the person from Kibi Support.

Request „Support Access“ from Kibi Support with reason, countdown, and the buttons „Reject“ and „Approve“

Revoke approval#

As long as no one has logged in yet, you can revoke the approval on the same page using Revoke approval. After that, no login is possible, and the request will be marked as Revoked.

Approved request with countdown and the button „Revoke approval“

End an ongoing session#

As long as someone is logged in with your account, the platform will display a notice at the top, for example, "Kibi Support is currently logged in with your account."

Notice „Doku System Admin is currently logged in with your account.“ with „View and end“

Click View and end in the notice.

Click End session. The other person will be logged out immediately and informed.

Request in status „Currently running“ with the button „End session“

For system admins: Log in as a person#

As a system admin, you can log in with another person's account, for example, to reproduce a problem. You always need their approval. There is no way around this.

Request approval#

Open the person's profile under Colleagues.

Select Actions ("...") → Log in as person at the top.

Opened action menu in the profile with the entry „Log in as person“

Under Reason, briefly describe what you want to help with (at least 10 characters). The person will see this reason.

Select Request approval.

Dialog „Log in as Annika Albrecht?“ with the field „Reason“

As soon as the person responds, you will receive a notification and an email.

Start login#

Open Administration → System → Audit and then the Access as Person tab. Here you will find all requests from all system admins in your company with their status.

For an approved request, select Log in now.

Tab „Access as Person“ with an approved request and „Log in now“

The session will open in a new tab. You yourself will remain logged in in your previous tab.

Warnung

If your browser blocks the new tab, allow pop-ups for the platform and try again.

At the top of the session tab, it will say, "You are logged in as ... Everything you do here happens with this account and is logged." Use End session to log out. After that, you can close the tab.

Session tab with the notice „You are logged in as Annika Albrecht“ and „End session“

When it doesn't work#

  • Only system admins can log in as another person.

  • Not as another system admin, not as yourself.

  • Not as Kai or as a service account.

  • Not with locked accounts, as the person might not see the request.

  • Not with people from other Kibi teams. They only log in to their own Kibi.

  • Not from an ongoing session as another person.

  • If the person has become a system admin since their approval or their account has been locked, the approval becomes invalid.

What is possible in a session#

Anyone logged in with a person's account sees the platform as they do, with their groups, files, appointments, and permissions.

Warnung

For system admins, this also applies to personal content: Chats, emails, notes, and conversations with Kai belonging to the person are visible in the session. The person's approval covers this. They should therefore be aware of what they are agreeing to.

Blocked in every session#

  • Works council area: remains locked, even if the person is a member of the works council.

  • Access data and security: Password, email address, two-factor authentication, passkeys, personal API tokens, "log out other sessions," and switching to another company. Only the person themselves can change these.

  • Personal login link: The person's own login QR code and login link cannot be retrieved.

  • Confirmations: Only the person themselves can confirm terms of use and privacy policies.

  • Delete or mute notifications: This ensures that no one can remove a notice that the person has received about the session.

  • Office and downloads via browser session: Pages that require their own browser login will not open in the session.

What the session does not change#

To ensure the session does not appear as the person's activity:

  • The person does not appear as "online."

  • Chats, notifications, and emails remain unread. There is also no read receipt.

  • The person's push notifications do not appear in the other person's browser, and their push notifications are not suppressed.

Content changed during the session appears in the respective history as changes made by the person.

Traceability and logging#

  • Login log: System admins can see every entry created during a session under Administration → System → Audit in the Login Log tab. It is marked as "Kibi Support," even if a system admin from your company was logged in. You can see who started a session in the Access as Person tab.

  • Logged-in devices: The session appears in the person's device list with a note.

  • Log at Kibi: Every support login is also logged centrally: who, when, for whom, for what reason, when approved or rejected, when started and ended. Entries cannot be changed or deleted afterward.

Login log with a line marked „Kibi Support“

Exception: Support login without approval#

In rare cases, Kibi Support can log in without approval, but only if it is technically absolutely necessary or there is another legal basis, and only with justification. This applies, for example, if the account or company is locked and the person could not see the request at all. Kibi logs these logins centrally. Any changes the support makes to other accounts during this time (for example, creating a login link or resetting two-factor authentication) appear in the login log as "Kibi Support," and the affected person will be informed.

Info

System admins in your company do not have this option. They always need the person's approval.

If someone creates a login link for another person (copied, as a QR code or PDF, via email) or sets their password, the following applies:

  • A warning message appears beforehand.

  • The action appears in the login log, including the type and originator.

  • The person is immediately informed in the platform and via email, even if "Do Not Disturb" is enabled, for example, "… has created a login link for you." Multiple identical actions within 10 minutes result in one notification.

  • If the link is sent to the person via email, this email itself serves as the notification.

The QR code for login is only shown in your own profile, never on another person's page.

Logged-in devices and new logins#

In the Security tab of your profile, you can see where your account is logged in:

  • Logged-in devices: Each device is listed once, whether it's a browser on a computer, phone, or tablet, desktop app, or Kibi app, with "Last active" and IP address. The current device is marked as "This device."

  • Log out: Immediately logs out a device. Whoever is using it must log in again.

  • That wasn't me: Logs out the device and informs your company's system admins. Afterward, you should change your password.

  • Recent activities: Your logins, created login links, and changes to your access, each with the device.

List „Logged-in devices“ with „This device“, „That wasn't me“, and „Log out“; IP addresses are hidden

Notification "New login to your account"#

If someone logs in to your account on a device you have never used before, you will receive a notification with the device, IP address, and time, also via email and even if "Do Not Disturb" is enabled.

  • During the first login, the platform only learns about your device. No notification is sent yet.

  • A private browser window is considered a new device each time.

  • For logins by Kibi Support or your administration, this notification is not sent. Instead, there is the request and the notice at the top.

Warnung

If that wasn't you? Open Security → Logged-in Devices in your profile, select That wasn't me for the unknown device, and change your password.