Internal tools

Custom intranet software built on governed data

Give employees one place to find current reports, answers, and operational context. Permute connects the underlying systems, reconciles their records, and governs access to shared views. Build the interface with your team or have our engineers build and maintain it.

Example workflow

Illustrative custom app · Sample data

Connected systems

Source records for this workflow

Permute data foundation

Connected records, shared rules, source evidence, and governed access.

Custom application
Governed view

Internal team view

Operations workspace

Revenue tracked

$1.24M

Open deals

47

Needs review

3

Team viewLatest updateStatus
Revenue by regionTodayCurrent
Weekly pipelineTodayCurrent
Board packetYesterdayReview

Every view uses the same approved definitions and source records.

This is an example layout with sample records. Connector availability varies by plan and source permissions.

The working view

Give each role a useful starting point

Finance sees cash and revenue by entity. Operations (with a different access scope) sees orders, exceptions, and inventory. Both work from the same source records and definitions.

Built on Permute

What makes it work

One answer across systems

Permute reconciles duplicate records and applies one metric definition across dashboards and reports.

Access by role

Zero-trust permissions give each team access to approved views of shared data.

Reports that stay connected

Dashboards and scheduled outputs stay connected to source records, with refresh status and evidence available when a number changes.

How it works

From scattered systems to one internal hub

  1. 01

    Connect the systems

    Bring finance, customer, and operating records into one governed workspace.

  2. 02

    Apply business rules

    Resolve record identity and source precedence, then use shared definitions for the figures teams rely on.

  3. 03

    Publish team views

    Give each role a dashboard or custom workspace with the answers and source evidence it needs.

Why build on Permute

Build on a foundation each new tool can reuse.

Permute connects systems, reconciles records, and keeps business definitions and source evidence in one place. Each application reuses that foundation (including its data access rules) instead of rebuilding the same integrations and logic.

Build with your own team through Permute Factory's API and SDK, or work with our engineers to build and maintain the application. Permute-hosted apps use Permute sign-in and app access checks. Each app checks which business data a person may see before returning it.

Built for this workflow

One internal view across the business

Build an internal hub for the reports, operating metrics, and answers employees use each day. Permute keeps the data, definitions, and permissions consistent behind every team view.

Questions teams ask

Can employees see different data in the same intranet?

Yes. Permute’s zero-trust permissions govern which views each role can open in the custom intranet.

Can the intranet use our existing ERP and CRM data?

Yes. Permute connects those records and presents approved metrics and answers in one internal view.

Can we build the interface ourselves?

Yes. Build with Permute Factory’s API and SDK, or have our engineers build and maintain the interface.

See this workflow on your data.

Bring a report or workflow you run today. We’ll map its source systems, business rules, access, and first custom view (including any approvals your team needs).