Use this rollout path to confirm billable internal seats, clean up documentation, approve limited Client View material, and keep PSA roadmap workflows separate until they are released.
The goal is to help a buyer start small without creating unclear access, overbroad reader assumptions, or accidental staff-seat replacement.
Start with Owner and Staff accounts for people performing internal operational work. These accounts are billable internal seats.
Capture client records, procedures, project context, changes, handoffs, and approved operational notes before expanding visibility.
Client View is read-only and limited to approved client-facing material. Keep passwords, secrets, internal projects, billing, automation, and staff workflows internal.
Core includes 25 Client View users per organization, or 5 per paid internal seat, whichever is higher. Larger client portal rollouts may require Client Portal Plus or a higher plan.
Approvals, project status, ticket visibility, notifications, evidence sharing, and PSA-linked collaboration belong in Client Portal Plus, PSA, or higher-plan discussions as those lanes mature.
Any user doing internal operational work must be Owner or Staff and must consume a billable seat. Client View cannot create, edit, delete, invite users, manage members, access billing, access passwords or secrets, view internal docs/projects, toggle visibility, export org data in bulk, run automation, or perform staff work.
Answers stay intentionally conservative so public copy does not overpromise availability, access, or billing treatment.
Start with the people who actually perform internal IT work as Owner or Staff users, then add approved read-only Client View access only where appropriate.
Use Client View only for approved client-facing material. It is not an internal workspace and does not replace billable Owner or Staff accounts.
Larger client portal rollouts, approval workflows, evidence sharing, notifications, and PSA-linked collaboration may require Client Portal Plus or a higher plan.
