Projects group related documents together under a single URL path. Teams control who can access what.
Projects
Every document belongs to a project. A project lives under an account and has its own slug, so document URLs follow the pattern /:account/:project/:filename.
Projects can be public (visible to anyone) or private (visible only to members). Private projects and their documents don't appear in search or listings for non-members.
Role system
pdrive uses a five-tier role system:
| Role | What they can do |
|---|---|
| Viewer | Read documents and version history |
| Editor | Everything a viewer can do, plus upload and edit documents |
| Manager | Everything an editor can do, plus manage members and project settings |
| Admin | Everything a manager can do, plus manage account settings |
| Owner | Full control, including billing and account deletion |
Roles apply at two levels. Account-level roles set the default for all projects in that account. Project-level roles can override the default for specific projects.
Invites and membership
Invite people to your account or to specific projects by username. Invitees receive a notification and can accept or decline. You set the role at invite time.
Members can belong to multiple accounts. Each membership tracks its own role independently.
Members-only projects
For documentation that only your team should see, set a project to private. Only members with an explicit role on that project (or an account-level role) can view it.
Combine private projects with the viewer role to share documentation with external reviewers without giving them edit access.