Roles and Actions in PTC Orbit
A consolidated view of every PTC Orbit role, the persona it belongs to, and the product capabilities each role can access.
Overview
PTC Orbit controls access through role-based assignments managed in Max Admin. Every user receives the Standard User role by default. A system administrator then assigns one of two primary roles: Orbit Admin or Orbit User. These primary roles determine which modules, pages, and actions a user can access. Beyond the two primary roles, administrators can create custom roles to match organization-specific job functions.
Three personas interact with PTC Orbit, each mapped to specific roles and responsibilities. The table below lists every role, identifies the persona it belongs to, and details the product capabilities and actions available to that role.
Primary roles
|
Persona
|
Role
|
Capabilities and actions
|
Capabilities not available
|
|---|---|---|---|
|
Administrator
|
Orbit Admin
|
All PTC Orbit capabilities. Includes:
• Create and manage roles, groups, and permissions in Max Admin
• Configure list views, forms, and dashboards
• Create and edit scoring models in Score Configuration
• Create and manage Service Campaigns and Revenue Campaigns
• Configure Data Foundry matching rules
• Access Applications settings
• All end user capabilities listed below
|
N/A
|
|
End User
|
Orbit User
|
Day-to-day operational capabilities:
• View and filter assets across List, Group, Location, and Map views
• View and manage Dashboards
• View and manage Accounts
• View Products
• Create and manage Work Orders
• View and triage Pending Items
• Use AI Hub for conversational analytics and 3D product exploration
• Use Demand Forecasting
• Use Global Search
• Manage App Notifications
|
The following are not available:
• Score Configuration
• Campaigns
• Data Foundry
• Applications
• Create Location, Create Asset, Add Part (disabled under Assets)
|
|
End User
|
Standard User
|
Default role assigned automatically to every new user. Grants baseline platform access. Must be combined with Orbit Admin or Orbit User to access PTC Orbit capabilities.
|
All PTC Orbit capabilities are unavailable until one of the two primary roles is also assigned.
|
Implementer role
Implementers operate outside the PTC Orbit application interface. They do not receive an in-app role assignment. Instead, they work directly with the underlying infrastructure and integration tools.
|
Persona
|
Role
|
Capabilities and actions
|
|---|---|---|
|
Implementer
|
Implementer (no in-app role)
|
• Provision and operationalize new tenants through the Tenant Management system
• Configure Matillion data integration pipelines for full and incremental sync
• Set up data connectors for Salesforce, AWS S3, and custom REST API sources
• Configure Snowflake environment settings and credentials
• Set up ServiceMax Core integration for bi-directional data sync
• Configure Windchill integration for product structure and BOM data
|
Custom roles
Administrators can create custom roles in Max Admin to match specific job functions within their organization. Custom roles inherit permissions from a parent role and restrict or extend access as needed. Common examples include:
|
Persona
|
Example role
|
Typical capabilities
|
Parent role
|
|---|---|---|---|
|
End User
|
Asset Manager
|
View and edit asset records, assign work orders, generate reports, manage accounts and products.
|
Orbit User
|
|
End User
|
Field Technician
|
View assigned work orders, update task statuses, view asset details. Cannot modify asset records or create new assets.
|
Orbit User
|
|
End User
|
Service Operations Manager
|
Review demand forecasts, monitor dashboards, triage pending items, manage campaigns.
|
Orbit User
|
|
End User
|
Maintenance Planner
|
Create work orders, manage campaigns, review asset scores and 3D product structure data.
|
Orbit User
|
|
End User
|
Audit-Only User
|
Read-only access for compliance reviews and regulatory audits. Cannot create, edit, or delete any records.
|
Orbit User
|
 |
These are examples only. Your organization defines its own custom roles based on operational requirements. For the procedure, see Creating Roles.
|
Role assignment
The system administrator (first user on a newly provisioned tenant) automatically receives the Orbit Admin role. All other users require manual role assignment. For details, see: