Security first

    Every action scoped, approved and logged.

    Every layer of Uniportal is designed with security at its core. The assistant inherits only the technician's permissions, and nothing that changes data runs without a person's approval.

    Pillars of Uniportal security
    01 · Tool permissions

    Admins decide which tools and actions an agent can use.

    Integrations you don't use stay locked. Turn each action on or off, scope it to an access group, and change permissions per role or team. Anything not allowed is denied by default.

    ActionAccess groupStatus
    ConnectWise · update ticketService deskOn
    IT Glue · read documentsEveryoneOn
    Entra ID · reset passwordService deskOn
    NinjaOne · run scriptSenior engineersOn
    Entra ID · assign admin roleNobodyOff
    02 · Human in the loop

    Nothing that changes data runs without a yes.

    Every action that modifies data needs explicit confirmation from a person before it runs. That is enforced in code, not just in policy, and every decision is logged to the ticket.

    Entra ID · Block sign-inWaiting for approval
    User: j.cole@hartwelldental.comWill not run until a technician approves.
    03 · Fine-grained access

    The assistant gets the technician's permissions. Never more.

    Assistants inherit the exact permissions of the technician who invokes them, with no escalation. Boundaries apply at four levels.

    Level 1Client
    Level 2End user
    Level 3Device
    Level 4Tool
    04 · Access token isolation

    The AI never sees a credential.

    The agent never stores or sees raw credentials or API keys. It asks the Uniportal backend to make a tool call, and the backend checks permissions before running the call with credentials it keeps encrypted.

    AI agentRequests a tool call. Holds no secrets.
    Uniportal backendChecks permissions, then calls the tool with encrypted credentials.
    Your toolsPSA, RMM, docs and identity.
    Platform controls

    Start locked down. Expand as trust grows.

    The assistant can't act without a technician's approval. Start restricted, and give it more autonomy over time.

    Human in the loop by design

    The assistant cannot act without technician approval. Start restricted and expand autonomy over time.

    SSO and role-based access

    Single sign-on, plus access controls by role and group.

    Permission inheritance

    The assistant takes on the technician's scope, limited by customer, user, device and action type.

    Full audit trail

    Every technician and AI action is logged with timestamp, actor, client context and outcome.

    AI chat oversight

    Admins can review AI chats across every technician, for training gaps and quality control.

    Full agent reasoning traces

    Each session keeps a complete trace of the assistant's reasoning.

    Encrypted credential storage

    Credentials and API keys are encrypted at rest. The assistant has no direct access to secrets.

    Credential isolation

    Every tool call goes through a backend proxy that checks authorization first. No credentials are exposed to the model.

    Multi-tenant data isolation

    Client data is isolated, with no cross-tenant access at the application or database layer.

    Running a security review?

    We'll take your security questionnaire and due-diligence questions, and walk you through how every action is scoped, approved and logged.