The Front Door for
Trusted Services
The Service Access Problem
Fragmented Access
Employees navigate a maze of different portals, forms, and email threads. No single source of truth for service access.
Loss of Control
Vendors own the intake experience. Customers lose visibility and governance over their own data.
Static Guidance
Process diagrams show "what to do" but not "how to do it." Employees still hunt for the right form or system.
Permittal Inverts the Model
Instead of sending employees to vendor portals, vendors deploy their services into your portal.
Scattered, chaotic access
Centralized, governed access
Built for Governance
Four architectural pillars that put control in your hands
Services are defined as versioned artifacts:
Portals always belong to the customer. Vendors integrate, they don't own.
Complete visibility into every request and action.
Turn static documentation into actionable workflows.
How It Works
Four steps to governed service access
Set It Up
Define the services your organization wants employees to access — internal teams and external vendors alike.
Approve
Choose what's available, who can use it, and where it appears.
Access
Employees open approved apps, start processes, or submit information in one controlled place.
Connect
Requests and actions flow securely into the systems that already do the work.
Works With the Tools You Already Use
- Send structured data to any system that accepts webhooks
- Secure, signed payloads for verification
- Integrates with Jira, ServiceNow, Slack, and custom platforms
- No required workflow engine or system replacement
Built for Controlled Service Access
- Customers decide which services are available and where they appear
- Vendors deploy into customer-controlled environments — not the other way around
- Every service is versioned and deployed intentionally
- Complete history of service changes and submissions
- Remove or replace vendors without breaking employee workflows