All topics

Getting started

Sign up, create a workspace, invite teammates, and add your first client.

Create your account + workspace

Sign up at app.phloz.com/signup with email + password, Google, or a magic link. On first login Phloz asks for a workspace name (your agency's name) and auto-suggests a slug — keep it short.

Every workspace starts free on the Starter tier (one active client, two seats). Upgrade anytime from Settings → Billing — proration is automatic.

Invite team members

Open /[workspace]/team and click Invite member. Pick a role (see roles below), enter the email, and optionally pre-assign clients (only meaningful when your workspace policy is "Restricted by assignment").

The invitee gets a magic link valid for 7 days. Owners + admins can resend or revoke from the same page.

Add your first client

From /[workspace]/clients click Add client. The form asks for the business name + a few optional fields (industry, budget, target CPA, geo targeting). Most fields are editable later from the client's overview tab.

Each client gets a unique inbound email address (e.g. client-xyz@inbound.phloz.com) — copy it from the client header to forward emails into the messages thread.

Roles & what each can do

  • Owner — sees everything, edits billing, transfers ownership. One per workspace.
  • Admin — invites + removes members, manages clients + groups + departments + access grants. Cannot edit billing or transfer ownership.
  • Member — sees only assigned clients (unless the workspace opts everyone in). Can edit tasks, messages, the tracking map for their assigned clients.
  • Viewer— read-only on assigned clients. Can comment but can't mutate anything else. Doesn't count against the seat cap.

Workspace access policy

Settings → Workspace → Client access. Two options:

  • Everyone sees everything (default) — every member sees every client.
  • Restricted by assignment — members and viewers see only clients granted to them, their department, or to a group containing the client.

Owners + admins always see everything regardless. The restricted policy is the right pick once you have multiple teams who shouldn't see each other's portfolios.