Identity
Access begins with authenticated users and Organization membership.
Security
Your company stays in control
Identity, permissions, data access, and deployment boundaries stay part of the operating system you build.
Path security modelControl follows context
Identity
01Access begins with authenticated users and Organization membership.
Permissions
02Roles and app permissions keep actions within the intended scope.
Data boundaries
03Organization and App context travels with every governed request.
Runtime separation
04Development, preview, and production remain distinct operating environments.
Control at every layer
Security stays connected to the people, data, Apps, and environments that define your company.
Permissions
Roles and app permissions keep actions within the intended scope.
Data boundaries
Organization and App context travels with every governed request.
Runtime separation
Development, preview, and production remain distinct operating environments.
Control travels with the work
People
Authenticated access
Organization membership and role-aware permissions
Apps
Scoped capabilities
App-specific roles and customer-app permissions
Data
Bounded context
Organization-scoped records, files, and integrations
Delivery
Separated environments
Controlled movement from building to production
AI within your boundaries
Path does not use your data to train models. AI works within the context and access you provide.
Governed intelligence
Context
AI receives the business context required for the task.
Access
Actions remain bound to the user and Organization scope.
Visibility
People stay close to the work, decisions, and results.
Evidence behind the platform
Review Path’s security documentation and current assurance materials in the Trust Center.
Open the Trust Center