The Team plan unlocks multiple AWS accounts per workspace. Connect production, staging, and subsidiary accounts under one workspace and run scans on each.
Limits
AWS connection limits by plan:
| Plan | AWS accounts per workspace |
|---|---|
| Free | 1 |
| Monthly Monitoring | 1 |
| Team Plan | 5 |
The limit applies per workspace, not per account. With 3 workspaces on Team, you could connect up to 15 AWS accounts across your organization (5 × 3).
Scan limits are shared at the account level — Team plans include 50 scans per month across all workspaces and connections. See Plan comparison.
How multi-account works
Each AWS account you connect is a separate AWS connection inside the active workspace:
| Per connection | Shared within the workspace |
|---|---|
| Unique AWS account ID (12 digits) | Workspace name and alert settings |
| Dedicated IAM role ARN | Team members with access |
| Unique External ID | Scan history (all connections) |
| Optional nickname and region | Monitoring schedule |
Parsivex never mixes data between AWS accounts. Each connection is verified independently, and scans run against one AWS account at a time.
Add another AWS account
Open Integrations
Go to Integrations (
/integrations) and find the AWS connections section. The usage meter shows how many of your 5 connections are in use.Click Add another AWS account
If you are under the limit, click Add another AWS account. This opens the onboarding wizard where you enter the new AWS account ID and set up a read-only IAM role.
Create a new IAM role in AWS
Each AWS account needs its own cross-account IAM role — you cannot reuse a role from another account. Follow Set up a read-only IAM role in the target AWS account.
Parsivex generates a unique External ID for each connection. Use the External ID shown in the wizard for that specific account. See External ID explained.
Verify and run a scan
Complete the verification step in the wizard. Once verified, the new connection appears in Integrations with its nickname and AWS account ID.
Start a scan from the dashboard to analyze that account. Each scan targets the AWS connection you select when starting it.
Scans run per account
Scans are tied to a single AWS connection:
- One scan = one AWS account — inventory, metrics, and Cost Explorer data come from that account only
- Scan history lists scans across all connections in the workspace, so you can track each account separately
- Recurring monitoring runs per workspace on its configured schedule; each monitored scan targets a connection in that workspace
- Findings and reports are scoped to the AWS account that was scanned
If you connect three AWS accounts in a workspace, run (or schedule) a scan for each account to get complete coverage.
Managing connections
In Integrations (/integrations) you can:
| Action | Details |
|---|---|
| View connections | See nickname, AWS account ID, and verification status for each |
| Add connection | Available until you reach 5 connections on Team |
| Remove connection | Permanently deletes the connection — this cannot be undone |
Removing a connection does not delete past scan reports, but you cannot run new scans against that account until you reconnect it.
Upgrade required?
Free and Monthly Monitoring plans support 1 AWS connection per workspace. If you try to add a second connection, Parsivex shows an upgrade prompt for the Team plan.
Upgrade to Team from Billing (/settings/billing) or the pricing page.
Troubleshooting
| Problem | What to try |
|---|---|
| "Upgrade to add more" | Multi-account requires the Team plan |
| At connection limit (5) | Remove an unused connection or add a new workspace |
| Verification fails for one account | Follow Connection troubleshooting — each account needs its own role and External ID |
| Wrong account scanned | Confirm which connection was selected when starting the scan |
| External ID mismatch | Each connection has a unique External ID — do not copy from another account |
Related articles
- Workspaces and switching — Separate environments with up to 3 workspaces
- Set up a read-only IAM role — Step-by-step IAM setup for each account
- External ID explained — Why each connection has its own External ID
- How scans work — What happens during a scan