Team & workspaces

Cost control rarely stays with one person. The engineer who can delete an orphaned volume is often not the person watching the bill, and the person watching the bill should not have to forward screenshots to get anything done. Parsivex handles that by letting you invite teammates into a shared workspace where everyone sees the same findings, the same savings, and the same alerts.

A workspace is the container for everything: the AWS connections it scans, the findings those scans produce, and the members who can see them. Most teams need one. You would add a second when the boundary is real — a separate client, a subsidiary, or an environment you want kept apart from the rest — and switch between them from the sidebar. Scans, findings, and alerts never leak across that boundary.

Larger estates are rarely a single AWS account, so a workspace can hold several connections, each with its own IAM role and External ID, each scanned on its own. The articles below cover sending and accepting invites, how seats are counted against your plan, connecting additional AWS accounts, and how switching workspaces changes what you are looking at. How many seats, workspaces, and AWS connections you get depends on your plan — the plan comparison article in plans and billing has the current numbers.