Welcome to Uniportal
What Uniportal does and where to start setting up your tenant.
Uniportal is an AI assistant for MSP helpdesk technicians. It works tickets alongside your team, pulling context and taking action across your PSA, RMM, documentation, and Microsoft 365. Every action routes back to a technician for review, so handing a task to the AI means approving what it did, not losing track of it.
Skills tell it how you want a given situation handled. Agent Tools are what it uses to act. Memories are what it already knows, about your MSP, a customer, a device, or an end-user, without you having to explain it again. Admins control which tools can run on their own, which need approval first, and who has access to what.
Why Uniportal
Your tickets, assets, documentation, and licensing live in different tools, and none of them can see across the others. Uniportal connects to all of them, so the AI working a ticket actually has the full picture, not just what's written in the ticket itself.
It's also built specifically for MSPs, not adapted from a general-purpose assistant. What it can see and what it's allowed to do are decisions made around how a helpdesk runs, and security and governance were part of that from the start.
Setting up your tenant
Order matters here. Skills and Agent Tools don't do much until the AI has something to act on and someone to answer to.
Connect Microsoft 365 or Google Workspace
Go to Integrations and connect Microsoft 365 or Google Workspace first. These are what create your customers as companies in Uniportal, and every other integration maps its records to those companies. Connect your PSA first and there's nothing on the Uniportal side to map to yet.
Connect your PSA and documentation system
Next, connect the tools you run tickets and assets through: your PSA, your documentation system, and your RMM. Map their companies to the ones Microsoft 365 or Google Workspace created. This is what surfaces Agent Tools automatically, so do it before anything below.
Invite your team
Go to Team & Roles and invite the people who'll be working alongside the AI. Assign a role, then set up Group access so non-admins can actually see their customers.
Decide what needs a human
Review Tool modes and set which Agent Tools the AI can run on its own versus which need approval first. Start conservative, loosen it once you trust the pattern.
Write or import your first Skill
Go to Skills and either write one for a procedure you repeat often, or import one from the Skills Library built for your stack. Test it against a real ticket before trusting it.
Where to go next
Integrations
Connect your PSA, documentation, and other vendors.
Team & Roles
Invite your team and set who can do what.
AI Assistant
Where technicians work tickets alongside the AI.
Agent Tools
What the AI can do on a technician's behalf.
Skills
Teach the AI how you actually want things handled.
Memories
What the AI already knows, without re-explaining it every time.