01
Organization access
Control who can build, operate, and manage resources in the Path platform.
Connect
Path feature guide
Give every person the access their work requires.
Design identity, roles, permissions, and data boundaries into each Customer app and Organization workflow.
Product screenExample data
app.path.dev/access
Path · AccessOrganization / Access
Roles and permissions
Add roleOwner
Customer app access
Operator
Customer app access
Partner
Customer app access
What this makes possible
Start with the work, then shape the system.
02
Customer app roles
Shape the roles and permissions end users need inside a deployed Customer app.
03
Data boundaries
Keep customer, team, and App data scoped to the people and workflows that should use it.
How to approach it
A practical starting path.
The exact implementation depends on your data, permissions, operating model, and connected systems.
- 01
List the actors
Name internal teams, outside partners, customers, and system processes separately.
- 02
Grant the minimum
Define what each role can see or change at the record and action level.
- 03
Test the boundaries
Verify expected access, denied access, account isolation, and revocation paths.
Keep exploring
Related systems and capabilities.
Build your version.
Start with one useful workflow, then connect the rest as the system proves itself.