The Portola platform
Configure the systems, roles and approvals around your operation. Portola maintains a shared operational ledger, so you can change where data comes from and where approved actions are sent while preserving workflow context, history and accountability.
01
Data sources · approved actions · system mappings
02
User roles · permissions · approval routes
03
Shared context · named actors · verified results
Connect → Coordinate → Verify
Configure where data comes from and where actions go.
Configure connections to approved OPC UA and other industrial data paths, MES, CMMS, QMS, ERP, inventory and planning. Map incoming signals and records to the affected work, and define which systems receive each approved update.
Add or replace source and destination systems as your operation changes.
Configure access and approval authority around your teams.
Configure user roles, permissions and approval routes by department, responsibility, seniority and operating scope. Define who can see each record, propose a response, approve a decision or authorize an external system action.
Your operating policy determines who can act and who must approve.
Confirm the result and trace every action to its authority.
Confirm that each connected system accepted the approved change. Link the result to the person or automated workflow that acted, the responsible role and department, the approval, the time and the supporting evidence.
Authorized reviewers can see who did what, in which department, and why.
Ownership, deadlines and workflow state persist through approvals, system interruptions and long-running tasks. Retries and idempotent actions keep repeated attempts from creating duplicate work.
Set access, approval thresholds and decision routes for each department, site and workflow. Specify what runs automatically and what needs a named approver. AI-assisted planning follows those rules; operators, PLCs and safety-control systems retain their plant authority.
Follow each input, decision, approval and system action through to its verified result. The record identifies who acted, their role and department, what changed, when it happened and who authorized it—with the evidence needed to explain the outcome.
Portola maintains its own operational ledger: a persistent record of inputs, decisions, actions and outcomes. Configurable connections separate that shared record from the systems supplying data or receiving updates, so changing either side preserves the workflow’s context and history.
Configure the systems that supply your data and the systems that receive approved actions. Portola’s operational ledger keeps the shared records, decisions and history connected as you add or replace either side. Adapt the connections while preserving the work and its audit trail.
Today
QuickBooks
Stripe
ShopifyConnected · no migration required
Where Portola fits
Portola maintains the operating record independently of individual providers. Workflows use that shared ledger, while configurable connections map incoming records and outgoing actions to the systems you choose.
Operational ledger
Preserves shared records and history across system changes.
Configurable connections
Maps data sources and approved actions to your chosen systems.
Configurable authority
Applies your roles, permissions and departmental approval rules.
Department-level audit trail
Links actors, departments, approvals and system confirmations.
Systems can change · the ledger preserves continuity
As your business grows
NetSuiteAdded over time · switched in phases
Keep
Start with what exists
Add
Connect systems as you grow
Switch
Change systems, preserve the operating record
Illustrative expansion and migration path. New and existing integrations, provider capabilities, and migration requirements are validated for each customer environment.
Configure who can see, propose, approve and act within each workflow. User roles, permissions and approval routes follow your departments, responsibilities and operating scope. A shared audit trail records who did what, in which role and department, when it happened and who approved it.
Back office workspace selected
Northstar workspace
Illustrative workflow
Northstar members
People share the account, with access shaped by role.
Maya’s workspace · Operator view
6
Open
2
Due today
18
Closed this week
Month-end close · MC-SEP-26
Connected systems · QuickBooks · Stripe · Bank
Impact
3 approvals
Progress
2 approved · 1 waiting
Due
Today · 3:00 PM
Live approval route
3 people · 3 departments · 3 approvalsConfirm accrual completeness
Approved · 2:42 PM
Approve inventory cutoff
Approved · 3:18 PM
Release the September close
Awaiting approval
Opened after AP + inventory approvals
Click the action to see the resulting decision, system records, and verification.
Illustrative workflow. Names, account records and outcomes are fictional sample data.
One account · Multiple users · Role-based access · Shared history
Configure its systems, user access and approvals, with a traceable record of every decision.