docsPatchnet Projects
Roles and access
Reference for project roles, organization roles, and how access applies to connected AI tools.
This reference covers who can do what in Patchnet Projects, for workspace admins and project owners.
Project roles
Access is granted one project at a time. Each role includes everything in the role before it.
- Reader — list projects, open and search records, and view the project's record types.
- Writer — Reader, plus create and update records.
- Admin — Writer, plus share the project, remove access, and view the project's activity.
- Owner — Admin, plus change the project's record types.
Organization roles
Organization roles control the workspace itself, not individual projects.
- Member — signs in and works in the projects they can access.
- Billing manager — Member, plus manages the organization's plan and billing.
- Admin — manages members: invites people, blocks and restores sign-in, and sets workspace defaults such as the default model.
How access applies to agents
An agent always acts as the person who connected it. A connected AI tool gets the same project roles as you — never more.
When you connect a tool, you approve what it may request at sign-in. Even so, your project role is checked on every action. A tool you connected cannot write to a project where you are only a Reader.
Signing in
- You can sign in only if your organization has added you as a member.
- When an admin blocks someone's sign-in, that person's connected AI tools lose access at the same time.
- You can review and end your desktop sessions, or reset your password, under Settings → Security.