Manage multiple sites from one org account
How to run a portfolio from the org dashboard — scope roles per site, aggregate billing, and read cross-site analytics in one surface.
An SGEN org account is the home for a portfolio of sites.
Instead of signing in to each site separately and reconciling billing across them, the org account holds the portfolio in one place — one set of users with per-site roles, one billing surface across every site, one analytics view that compares performance across the whole estate.
This page is the operator's walk-through of the org-account surface.
It covers four things — orienting in the org dashboard, scoping a team member's access to specific sites, reading the aggregated billing surface, and working with cross-site analytics.
The page is written for an agency principal, an in-house multi-site lead, or any operator running more than one site under one account.
A single-site owner does not need this page; the per-site admin covers everything for that case.
What is this for?
Use this page when an org account holds more than one site and a team member or system needs to act on the portfolio as a whole.
Common situations are onboarding a new team member with access to the right subset of sites, reviewing the bill across the portfolio at the start of the month, and producing a comparison across sites for a quarterly review.
The page covers the SG-Dashboard org surface.
It does not cover the per-site SG-Admin — every individual site keeps its own admin, and the per-site documentation continues to apply once you are inside one.
A useful mental model — the org account is the lens; each site is the picture.
Most day-to-day work happens at the per-site lens; the org lens carries the questions that span sites or summarize across them.
Good use cases
- An agency principal manages ten client sites and wants every team member to see only the sites they actively work on.
- A new contractor joins for a one-month engagement and needs read access to three sites with no edit rights.
- The bookkeeper needs the invoice for the whole portfolio for the month with a per-site cost breakdown.
- A growth lead wants to compare conversion rate across five product sites with the same shape.
- A site is being offboarded from the agency and needs the user list and the billing line cleaned up.
- The team is preparing a quarterly review and needs the high-level performance numbers for every site in one view.
- A new client signs and the agency needs to provision a fresh site with the right roles and billing route in under an hour.
What NOT to use this for
- Per-site content editing.
- Cross-site content syndication.
- Per-user 2FA setup.
- White-label of the SGEN admin itself.
How this connects to other features
- SG-Dashboard Overview — the structural definition of the org account surface that this page operates against.
- Client Manager — the surface for end-client visibility within an agency context.
- Billing Overview — the reference for invoice shape, payment methods, and subscriptions.
- Audit Log — every role change, invitation, and billing-method change at the org level appears in the log.
Before you start
- You are signed in as a user with org-admin permission.
- The portfolio is set up — every site you want to manage is already provisioned under the org account.
- For role changes, you know the email of the team member and the sites they need access to.
- For billing review, you know the period the review needs to cover and any cost-center allocation the bookkeeper expects.
- For a portfolio-wide change (tag taxonomy, role template, bulk plan adjustment), the team is informed so no one is mid-edit on a surface affected by the change.
Where to find it
The org-level surface is SG-Dashboard at the root of the account.
Sign-in lands here for an org-admin.
The left navigation carries the top-level surfaces — Sites (the portfolio index), Members (org-level users with per-site scope), Billing (the aggregated billing surface), Analytics (cross-site analytics), Org Settings (account-level configuration including SSO and branding).
Each site in the portfolio is reachable from the Sites surface; clicking a site opens that site's SG-Admin in a new tab with the org context preserved.
A search box at the top of the Sites surface accepts both site-name and tag substring matches.
Use it to jump straight to a known site when the portfolio is too long to scroll.
The combination of search plus saved filters keeps a large portfolio feeling small in daily use.
Steps
The workflow has four parts — orient in the dashboard, scope per-site roles, work the billing surface, and pull cross-site analytics. They are independent; do whichever applies.
1. Orient in the org dashboard
Open SG-Dashboard.
The landing page shows the portfolio summary — site count, total storage, total bandwidth, current month spend, and any sites that have entered an alert state.
The Sites surface lists every site in the portfolio.
Each row shows the site name, the public URL, the plan tier, the last-published timestamp, and a health indicator.
The health indicator combines uptime, recent error rate, and pending alerts into one signal.
Filter the Sites surface by plan tier, by health state, or by tag.
Tags are operator-defined on each site — useful tags carry the client name, the engagement type, or the lifecycle phase.
A typical agency tags sites with the client name and an engagement state such as active, paused, or offboarding.
Click a site row to open it.
The detail panel shows quick actions — open the admin, view recent activity, jump to billing for the site, see the user list for the site.
The detail panel also surfaces the last three log entries from the site, so a quick "what happened here recently" answer is one click away.
For a portfolio that has grown past twenty sites, use Saved Filters to keep the daily landing view manageable.
Save the filter combinations that match the team's read habits — active commerce, offboarding queue, pilot phase.
The Saved Filters dropdown sits at the top of the Sites surface for one-click recall.
2. Scope roles per site
Open Members in the left navigation.
The Members surface lists every user on the org account with their org-level role and the sites they have access to.
To invite a new team member, click Invite Member in the top right.
The invitation panel opens.
Enter the Email of the team member.
Pick the Org Role — Owner, Org Admin, or Member.
Org Admins see the full org surface; Members see only the sites assigned to them.
The Site Access section lists every site in the portfolio.
Tick the sites the team member should access.
For each ticked site, pick the per-site role — Site Admin, Editor, Author, or Viewer.
The roles map to per-site permissions and are documented in each site's Users surface.
Click Send Invitation.
The team member receives an invitation email with a sign-up link.
The link expires in seven days; resend from the Members surface if it lapses.
To change a member's access after invitation, click the member row.
The detail panel opens with the same Site Access list.
Tick or untick sites, change per-site roles, then click Save.
Changes take effect immediately on the member's next page load.
The audit log records both the inviter and the role change.
To remove a member from the org, click Remove Member in the detail panel.
The member loses access to every site under the org; their per-user account itself is not deleted — they can be re-invited later if needed.
For consistent invitations across many onboardings, use a Role Template.
Open the Templates tab on the Members surface, build a template with the org role, the site set, and the per-site roles, then save.
Future invitations pick the template from a dropdown, which removes the chance of one missed tick changing access for a new hire.
3. Aggregate billing across the portfolio
Open Billing in the left navigation.
The Billing surface opens to the current period summary — total amount, payment method on file, next invoice date, and any pending payment alerts.
The Invoice tab lists every past invoice for the org.
Click an invoice to expand.
The expanded view shows the per-site breakdown — every site that contributed to the invoice, with the line items for plan, overage, and any add-ons.
Use this view at month-end for cost-center allocation.
The Payment Methods tab manages the cards or accounts on file.
The portfolio can carry one default method that handles every site, or per-site overrides for cases where a specific client funds their own bill.
Click Add Payment Method to register a new method; pick Set as default for all sites or assign the method to specific sites.
The Subscriptions tab shows the active plan per site.
From here, upgrade or downgrade an individual site's plan, or apply a bulk plan change across a set of sites.
Bulk changes require confirmation; a preview shows the cost impact before commit.
To export a slice for the bookkeeper, click Export in the Billing top right.
Pick the period, the format (a printable form for sharing or a spreadsheet for review), and the level of detail (summary by site, or full line-item detail).
The export runs in the background and lands in the Exports tab for download.
4. Pull cross-site analytics
Open Analytics in the left navigation.
The Analytics surface opens to a cross-site comparison view.
The default view shows traffic, conversion, and uptime per site for the current period.
Each metric is one column; each site is one row.
Sort by any column to find the top or bottom performers on the dimension that matters.
Switch the period from the picker in the top right.
Available periods include Last 7 days, Last 30 days, Last quarter, and a custom range.
To compare a specific subset, tick the rows on the left and click Compare Selection.
The view narrows to those sites and switches to a side-by-side chart for the selected metric.
Each site name in the Analytics view links through to the per-site Analytics inside that site's SG-Admin.
Use the per-site surface for the page-level breakdown; use the org surface for the cross-portfolio comparison.
For a scheduled report, click Schedule Report in the top right.
The schedule panel lets you pick the metrics, the cadence (weekly or monthly), the format, and the recipients.
Scheduled reports land in the recipients' email at the scheduled time and are recorded in the Audit Log.
What success looks like
A well-run org account shows each of four signals.
The Sites surface fits on one screen for portfolios under twenty sites, with each row green on health and tagged for fast filter.
The Members surface lists every team member with a current role and no orphan invites.
The Billing surface shows the next invoice with a confident estimate and no pending payment alerts.
The Analytics surface answers "how is the portfolio doing this period" in under a minute.
A new team member onboarded through the org account is signed in within an hour of the invitation, sees only the sites they should, and shows up correctly in the Audit Log on their first sign-in.
A large portfolio adds a fifth signal — the team can answer "where are we spending the most" and "which site grew the most this quarter" in under a minute by reading the Billing and Analytics surfaces together.
A team that can answer those two questions quickly is a team that runs its portfolio rather than chasing it.
What to do if it does not work
- Team member invited but cannot sign in.
- Member sees more sites than expected.
- Billing total seems higher than expected.
- Per-site role change did not take effect.
- Analytics shows a site with no data.
- Sites surface health indicator stuck on a red state.
- Bulk plan change preview shows a price that looks wrong.
- A site appears in the portfolio that was supposed to be removed.
Examples
Example A — onboarding a contractor with read-only access to three sites.
Principal opens Members, clicks Invite Member, enters the contractor's email, picks Member as the org role, ticks three sites under Site Access with Viewer role on each, and sends the invitation.
Contractor signs in within two hours.
The Sites surface for the contractor shows three sites; opening any site lands them in a read-only SG-Admin.
Audit Log records the invitation, the contractor's first sign-in, and every page view.
Example B — month-end billing review for a ten-site portfolio.
Bookkeeper opens Billing, clicks the most recent invoice, expands the per-site breakdown.
Two sites show overage on bandwidth.
Bookkeeper exports the invoice as a spreadsheet with line-item detail, allocates costs to client codes in the spreadsheet, and flags the two overage sites to the principal.
Principal opens each overage site, reviews traffic in Analytics, and either upgrades the plan or accepts the overage as a one-time event.
Example C — comparing conversion across product sites.
Growth lead opens Analytics, ticks the five product sites, clicks Compare Selection, picks Conversion rate as the metric, and sets the period to last quarter.
The side-by-side chart shows two sites at the top of the range, three in the middle.
Growth lead opens the top performer's per-site Analytics, reads the page-level breakdown, and exports the insight for a team review the next morning.
Example D — offboarding a client site with full evidence.
An agency reaches the end of an engagement and needs to close out the relationship cleanly.
The principal opens SG-Dashboard, finds the client site in the Sites surface, opens the detail panel, and runs through the offboarding checklist — revoke per-site role from every agency team member, tag the site as offboarding, take a final manual backup labeled engagement-end-archive, run an Audit Log export for the engagement period, transfer billing ownership to the client.
Each step appears in the Audit Log.
The principal hands the export and the backup reference to the client; the agency relationship closes with a clean record.
Example E — provisioning a new client site under the existing org.
An agency lands a new client and needs to spin up a site under the org account.
The principal opens SG-Dashboard, clicks Add Site, follows the new-site wizard, tags the site with the new client's name, sets up per-site roles for the assigned team members, and pins a billing line under the right payment method.
Within an hour the new site is ready for build work, the right team has access, the bill is correctly routed, and the Audit Log carries the full provisioning trail.
Plan for agency and enterprise multi-site scenarios
Five sites under one account is a comfortable setup. Twenty-plus sites is a different operation. Habits that the small case can do informally need to become explicit at scale.
Tag taxonomy
A small portfolio runs fine without tags; a larger one needs them.
Build a tag taxonomy and apply it consistently.
Three dimensions usually carry the operation — client (the name on the contract), engagement state (active, paused, offboarding, archive), and site type (marketing, commerce, app, landing).
Apply the tags on every site.
Use the Sites filter to slice the portfolio by any tag combination.
A principal running a quarterly review filters to active plus commerce for the commerce-active subset; the bookkeeper filters to active for the full billing roster; the offboarding lead filters to offboarding for the closure queue.
The taxonomy is operator-defined; document it once in the team's runbook so new team members apply the same tags the same way.
The portfolio's value grows with the tag discipline.
Role-template discipline
For a team that adds and removes contractors regularly, role decisions on every invitation slow the team down.
Build role templates.
Pick three or four common shapes — agency-editor, agency-admin, client-viewer, contractor-readonly — and write down which sites and which per-site roles each one carries.
When a new team member joins, pick the template and apply it.
The Members surface accepts the same set of ticks every time; the per-site role assignments mirror the template.
The Audit Log carries the role assignment for every new member with the same shape, which makes review faster three months later.
When a team member moves from contractor to permanent, switch the template.
The role change appears in the log with the right context.
A team that runs templates is a team that catches role drift early.
Billing-allocation patterns
For an agency that resells SGEN to clients, the billing surface carries the decisions.
Two common patterns.
First, the agency holds the master billing relationship and re-bills clients separately; per-site cost data drives the re-bill.
Second, each client funds their own site directly through a per-site payment method override; the agency manages but does not pay.
Pick the pattern up front and document it.
Switching mid-engagement is painful; clarity at the start avoids the switch.
The bookkeeper carries the pattern in the close-out runbook; the principal carries it in the engagement-pricing conversation; the Audit Log carries every billing-method change so the trail is intact.
For larger enterprise portfolios — fifty or more sites — schedule a quarterly billing review.
Open Billing, expand the last three invoices, scan for overage trends, surface them in the review.
Trends often hide in plain sight; a quarterly check catches the pattern before it becomes a budget surprise.
Onboarding and offboarding runbooks
Document the onboarding flow for new team members.
The runbook names the email, the role template, the per-site assignments, the Audit Log verification step, and the first-week check-in.
New team members are signed-in, productive, and visible in the log within hours, not days.
Document the offboarding flow with equal precision.
Revoke roles, retag the site if the engagement is ending, export the relevant Audit Log slice for the engagement period, run a final backup.
A clean offboarding produces a record the team can reach for if a question comes up six months later about what happened on a closed engagement.
Common questions about managing multiple sites
Can one user have different roles on different sites?
Yes.
The per-site role is set on the Members surface and applies only to that site.
A team member can be a Site Admin on one site, an Editor on another, and a Viewer on a third.
The combinations are flexible and recorded per site.
Does the org account add a separate billing line for each site?
The org account aggregates billing into one invoice per period, with a per-site breakdown inside the invoice.
The bookkeeper sees one charge on the team's payment method and one document for accounting, with full per-site detail one click away.
Can the agency hide some sites from a client logging into the org?
Per-site roles handle visibility.
A client signed into the org account sees only the sites where they hold a per-site role.
Sites the client is not assigned to do not appear in their Sites view.
The Members surface carries the assignments; review them on every onboarding cycle.
What happens to a site if the org account is suspended for non-payment?
Sites under a suspended org enter a graceful-degradation state — public visitors still see the site for a short window, but admin actions are restricted.
The full grace window depends on the plan tier.
Resolving the payment lifts the suspension; the Audit Log records the suspension entry and the lift.
Can I move a site between org accounts?
Site transfer is supported through the platform support flow.
Open a support request with the source org, the destination org, and confirmation from both sides; the platform performs the transfer with a brief maintenance window.
The Audit Log on both orgs records the transfer.
How do I export every Audit Log entry for an entire portfolio?
Open SG-Dashboard → Activity.
Set the date range, filter to the event families that matter, click Export.
The export covers every site in the portfolio in one file.
For per-site bundling, run the export from each per-site Activity Log surface separately; the file then carries one site's events for the chosen window.