Live IT documentation for teams that need cleaner records and safer client-facing access.

Use Client View for approved visibility, not internal operations.

Client View is designed for read-only access to approved client-facing material. It is useful for sharing selected information without exposing internal workspaces or turning client accounts into staff seats.

• Approved client-facing documentation and handoff material.
• Read-only evidence or status material that has been intentionally shared.
• Client-facing procedure references that do not expose passwords, secrets, or internal controls.

Internal operational work requires a billable Owner or Staff seat.

Any user performing internal operational work must be Owner or Staff and must consume a billable internal seat. Client View cannot create, edit, delete, manage members, access billing, view secrets, run automation, toggle visibility, or bulk-export organization data.

Larger client portal rollouts, approval workflows, evidence sharing, notifications, and PSA-linked collaboration may require Client Portal Plus or a higher plan.

Roll out IT Docs while keeping Client View separate from staff seats.

The implementation path keeps paid internal work separate from approved read-only Client View access. Start with Owner and Staff seats for internal operators, then publish selected client-facing material only after it is reviewed.

• Confirm billable Owner and Staff users.
• Review the Client View allowance before inviting client-facing readers.
• Keep passwords, secrets, internal projects, billing, automation, and staff workflows out of Client View.
• Use procurement, trust, and support routes for buyer review before wider rollout.