---
title: "Portal connections"
description: "Portal connections"
---

An agent works in the pages of a portal the company uses, such as an ERP. The person logs in to the portal on a Siglata page with their own password and codes, which the agent never sees; Kernel, Siglata's browser provider, keeps the session and logs in again on its own. Banks, social networks and the gov.br login are refused.

Browser time is charged to the organization's credits, including failed executions. Before opening a browser, Siglata reserves the call or session time limit; closing releases unused credits. Calls in one session run in sequence, and charges and history are saved together. When the portal logs out, the tool logs in again with the stored login; only when that fails or asks the person for something does it fail with `portal_needs_login` and the link for the person to log in.