Principals represent identities in Plinqx - both human users and AI agents. Understanding principals is key to managing access and audit trails.Documentation Index
Fetch the complete documentation index at: https://hypha-docs.plinqx.app/llms.txt
Use this file to discover all available pages before exploring further.
Principal Types
Plinqx supports four principal types:| Type | Description | Use Case |
|---|---|---|
| USER | Human users accessing the admin portal | Team members, administrators |
| SYSTEM | System-level operations | Background jobs, automated processes |
| INTEGRATION | External integrations and AI clients | API keys, automation tools |
| EXTERNAL_APPROVER | External parties for approvals | External stakeholders who approve requests |
Managing Principals
Creating Principals
Assigning Profiles
Principals are assigned RBAC profiles that determine their permissions:- Administrator: Full access to all features
- Developer: Access to tools, collections, and testing
- Viewer: Read-only access
- Custom: Custom profiles with specific permissions
Profiles define what actions a principal can perform. See Profiles & Permissions for details.
Principal-Based Audit
All actions in Plinqx are attributed to principals:- Tool Executions: Tracked by principal
- Configuration Changes: Who made the change
- Approval Decisions: Who approved/denied
- API Requests: Which integration made the request
Next Steps
Set Up Profiles
Configure RBAC profiles for principals
View Audit Logs
See principal activity in audit logs