Skip to content
PortalBase

Integrations

People come and go in your directory. PortalBase keeps up.

Connect your company sign-on and directory, and people are added and removed automatically. Start with a CSV for people, sites and assets. Use the documented API and webhooks to connect anything else, and let an AI assistant work through the same door your people use, with the same permissions.

Also calledAPI, Webhooks, Single sign-on, Directory sync, MCP connector

Used in

The solutions that put this product to work.

In the app

Set it up once, on the web.

  • 01Single sign-on where you run it.
  • 02CSV import, an API and webhooks.
  • 03An MCP connector for AI assistants.

Setup

Tiles, names and color

Your tiles

TasksShown on every crew member's home
TrainingShown on every crew member's home
Site walksShown on every crew member's home
FormsShown on every crew member's home
Safety talksShown on every crew member's home
Shift notesShown on every crew member's home

Your color

Headers, icon squares and chips follow your logo color, on the phone and on the web.

Sample company and data, made up for the picture.

What connects, and when

In order.

  1. Step 1

    Day one

    CSV import and export for people, sites and assets. Company sign-on with automatic provisioning.

  2. Step 2

    Next

    HR system sync for people, roles, sites, hires and terminations.

  3. Step 3

    Later

    Maintenance systems, to send repairs out and pull asset lists. BI feeds.

  4. Step 4

    From the start

    A documented public API and webhooks, so you can connect anything else.

Company sign-on

The directory you already run.

Microsoft Entra, Okta and Google. People are added and removed automatically. Directory groups map to roles.

Crews without a company email. They sign in by text message code, employee ID and PIN, or a QR badge on a shared device. You pick which.

One owner per field

No two systems fighting over a name.

One system owns each connected field. You set the direction at setup.

Writing back is supported. A change in PortalBase can go back to the system that owns it.

AI native

Anything a person can do, an assistant can do.

01

MCP connector

Claude, ChatGPT and other assistants connect to your PortalBase through a standard connector.

02

Same permissions

An assistant gets what the person who authorized it gets. Every action is logged the same way.

03

Revoke it

Your admin authorizes each connection and can pull it back. Your admin also sees every connected agent and what it did.

Your records leave with you.

A company can export everything, records, media and history, in open formats. Self-serve, any time.

Tell us what it has to connect to.

Your HR system, your maintenance software, your BI tool. We'll say plainly what's day one and what's later.

Book a walkthrough