Your team gets its own logins, with the right access for each person
You can invite teammates as Admin or read-only User, sort each client's sites with folders and tags, and keep a record of every configuration change.
Periodic reports stay organized by workspace
Reports are not a separate export workflow. WebPixie generates a workspace-wide digest that covers every resource in the workspace, sites and uptime monitors alike, and emails it to everyone in the workspace on the cadence included in that plan.
PDF report output
Each report summarizes the reporting period across the workspace: uptime status, the uptime, SSL, and domain incidents detected, common issues across sites, and site WebPixie Scores.
Email delivery
Reports are generated automatically and emailed as PDF attachments to every member of the workspace, so no one has to export them manually.
Plan-based cadence
The report schedule follows the active subscription for the workspace, so client or environment reporting stays aligned with the plan.
Current report intervals
Free: monthly; Starter: bi-weekly, monthly; Pro: weekly, monthly; Enterprise: weekly, bi-weekly, monthly
workspace-report.pdf
The PDF is workspace-contextual: it rolls up the checks available for the sites and monitors in that workspace.
You know exactly what each workspace role can do
Here is what each workspace role can and cannot do, from full control down to read-only.
OWNER controls workspace administration and billing. ADMIN manages monitoring resources. USER can review workspace data without changing configuration.
How workspaces work in WebPixie
WebPixie organizes monitoring into workspaces. A workspace holds your sites, monitors, incidents, and reports. You sort sites with folders, and tag sites and monitors by client, brand, or environment. Every member of a workspace has a role that sets what they can do.
There are three roles. OWNER has full control, including billing and team administration. ADMIN manages monitoring resources such as sites, uptime monitors, and incidents. USER has read-only access. Roles apply at the workspace level, which keeps access simple to reason about.
The workspace owner invites teammates by email; how many members a workspace can have depends on its plan. Every configuration change is recorded in an audit trail, and ownership can be transferred when the team changes.
Roles and setup are covered in the workspace docs.
Sites organized with folders and tags
Clients, brands, or environments kept separate
You can put each client’s or brand’s sites in a folder and tag sites and monitors by client or environment, then filter to one at a time. A separate workspace, on its own plan, is only for someone outside your team who needs their own login.
Access control with three roles
OWNER, ADMIN, and USER at the workspace level
Roles keep access clear. OWNER holds workspace administration and billing, ADMIN manages monitoring resources, and USER has read-only access. Roles apply across the workspace, so you grant the right level once instead of managing access site by site.
Email invitations for your team
Up to three pending invitations per workspace
You add teammates by email invitation, with up to three invitations pending at a time per workspace. People accept, take on their role, and start working in the shared workspace, so you never have to share a single login.
Changes tracked in an audit trail
Configuration changes recorded, ownership transferable
When several people manage monitoring, you need to know who changed what. WebPixie records configuration changes in an audit trail, and ownership of a workspace can be transferred when responsibilities shift, so the workspace outlives any one account.
Your team in one workspace
You invite teammates with roles and an audit trail. The plan comparison shows team limits.
Everything you need to monitor a website. In one workspace.
A quick look at other WebPixie features.
Why teams choose WebPixie for workspace management
Clients and environments kept apart
You group sites into folders and tag sites and uptime monitors by client, brand, or environment. When someone outside your team needs a login, you can give them a separate workspace on its own plan.
The right access for each person
Three workspace-wide roles, from full control to read-only.
A record of every change
An audit trail of configuration changes and transferable ownership keep the workspace accountable as the team changes.
Frequently Asked Questions
Common questions about workspace management.
Yes. The simplest setup is to add every client site to a single workspace and organize it with folders and tags, so one dashboard covers your whole client list. Workspace management lets you put each client's sites in a folder and tag sites and uptime monitors by client, contract or project, then filter by a tag to focus on one client. For each site you choose which checks run, such as uptime, SSL, DNS, domain and link checks. Site and monitor limits apply per workspace and depend on the plan: Free (1 site), Starter (10 sites), Pro (50 sites), Enterprise (unlimited). A plan belongs to one workspace, so opening a separate workspace for every client means a separate subscription for each one. You can compare limits on the pricing page and see agency workflows under solutions for agencies.
Your team shares one workspace, and each person gets the Owner, Admin or User role that fits their job. As workspace management describes, Owners control billing, membership and workspace settings, Admins manage sites, uptime monitors and incidents, and Users have read-only access. On paid plans, everyone sees the same incident during an outage, with its severity, affected resource and duration. Admins can add a note to it, such as what the host said or when the client was told, so whoever picks it up next has the context. Every configuration change is recorded in an audit trail. User limits depend on the plan, so you can compare team capacity on the pricing page.
Yes. Once the client contact has joined the workspace, the owner can transfer ownership to them, and the client then controls the workspace settings, membership and billing. This works well when you set up monitoring for a client in a workspace that holds only their sites: you configure the sites and uptime monitors, invite the client, and hand the workspace over when the project ends or the client wants to pay for it directly. Your team can stay on as members if the client keeps you in the workspace. Only the owner can transfer ownership, not an admin. The workspace management page explains roles and invitations, and the pricing page shows what each plan includes.
Yes. Each service you run on its own subdomain, such as an API, an app, docs or a marketing site, can be a site in one workspace, with its endpoints added as uptime monitors. Uptime monitoring gives each endpoint its own method, headers, auth, accepted status codes, keyword check and interval, so a payment API and a docs page can follow different rules. For each site you choose which checks run, such as SSL, DNS and domain monitoring, and the Certificates Manager lists subdomains seen in Certificate Transparency logs, so you can add the ones you missed. Tags label monitors by service and environment and let you filter to production or staging, and per-resource notification settings decide which monitors send alerts. Capacity depends on the plan: site limits are Free (1 site), Starter (10 sites), Pro (50 sites), Enterprise (unlimited), and uptime monitor limits are Free (3), Starter (20), Pro (50), Enterprise (unlimited). You can compare all limits on the pricing page.
Yes, through a workspace that holds only that client's sites, because WebPixie roles apply to a whole workspace rather than to single sites. If you invite a client contact with the read-only User role to your shared agency workspace, they will see every site in it, including other clients' sites. Inside your agency, one workspace with a folder per client is enough, and nothing in it is visible to anyone outside your team. Once a client should log in, their sites belong in a separate workspace that runs on its own plan: either the client pays for it and invites your team as Admins, or you run it for them. Each plan has its own user limit, so it is worth checking that it leaves room for the client and your team. Inside that workspace the client can follow uptime, incidents, WebPixie Site Score and the periodic PDF report without changing any settings. You can see how roles work in workspace management and compare user limits per plan on the pricing page.
Yes, WebPixie can monitor staging, development and preview environments the same way as production, as long as their URLs are reachable from the internet. Protected staging works too: uptime monitoring can send Basic, Token or Digest credentials or custom headers, check the status codes you accept and require a keyword in the response. For certificate and domain checks, you can add staging as its own site so it gets daily SSL monitoring and expiry warnings; each site counts toward your plan's site limit. You can tag staging, development and production monitors by environment to filter them in the dashboard and the API, and turn off notifications for monitors that should stay quiet. During a deploy, you can pause the staging monitor and resume it afterwards; the paused time does not count against its uptime rate. Keeping every environment in one workspace with tags means one plan covers them all. You can compare site and monitor limits on the pricing page.
Ready to organize your team?
Workspaces, three roles, invitations, and an audit trail.