Most accessibility conformance platforms support managing multiple sites from one account through a portfolio or workspace structure. A single login provides access to several properties, each with its own audit data, scan results, and remediation tracking, while a top-level view consolidates progress across the portfolio. This setup is standard for agencies, enterprises with multiple brands, and organizations operating distinct domains under one accessibility program.
| Capability | What It Means |
|---|---|
| Portfolio View | One dashboard summarizing conformance status across every site in the account. |
| Per-Site Workspaces | Each site has isolated audit data, scan schedules, and remediation tracking. |
| Role-Based Access | Permissions can be set at the account level or restricted to specific sites. |
| Consolidated Reporting | Reports can be generated for one site, a group of sites, or the full portfolio. |
How Multi-Site Accounts Are Structured
Platforms typically organize multiple sites under a parent account or organization. Each site exists as its own workspace, with separate audit reports, scan schedules, issue lists, and remediation status.
The parent account holds billing, user management, and the portfolio dashboard. Site workspaces hold the working data. This separation keeps remediation work for one property from blending into another.
What the Portfolio Dashboard Shows
A portfolio dashboard rolls up data from every site in the account into one view. Common elements include the number of open issues per site, conformance status against WCAG 2.1 AA or 2.2 AA, last scan date, and audit recency.
This view is useful for accessibility program managers who oversee several properties and need to see which sites are progressing and which have stalled. It is also the layer where leadership reporting happens, since it presents the full program in one place rather than site by site.
User Permissions Across Sites
Role-based access controls determine who can see and act on what. A platform administrator can usually assign permissions at three layers:
- Account level: full access to every site, billing, and user management.
- Site level: access limited to one or more specific properties.
- Role level: permissions tied to function, such as auditor, developer, viewer, or reporter.
Agencies often use site-level access to give each client visibility into their own property without exposing other clients. Enterprises use role-level access to separate developers working on remediation from executives reviewing reports.
Scans and Evaluations Across Multiple Properties
Scan scheduling is configured per site. Each property can have its own cadence (daily, weekly, monthly, or custom) based on update frequency and risk profile. Authenticated page scanning is set up per site as well, since each property has its own login flow.
Audits are scoped to individual sites. A portfolio account does not change how an audit is conducted; it changes how results are stored and reported. An audit completed for one site populates that site’s workspace, and the portfolio dashboard reflects the updated conformance status.
Reporting Across the Portfolio
Multi-site accounts support reports at three levels: a single site, a group of sites (such as all properties in one region or business unit), and the full portfolio. Reports can cover open issues, remediation progress, conformance status, and scan history.
For organizations preparing leadership updates or board reporting, portfolio-level reports condense a broad accessibility program into a format that conveys overall health without requiring a walkthrough of every site.
When Multi-Site Management Matters Most
The structure is built for organizations running coordinated accessibility programs across more than one property. Common situations include parent companies with multiple brand sites, agencies managing client portfolios, government entities operating departmental sites under one program, and enterprises with regional or product-line domains.
For organizations with a single site, multi-site capabilities add complexity without benefit. The structure becomes valuable when there are enough properties that tracking them in isolation creates reporting and oversight problems.
Multi-site account management consolidates oversight without merging the underlying work. Each site keeps its own data and remediation track, while the portfolio layer gives the program a single point of reference.