How to Set Up SiteGround for Small Teams

Getting SiteGround configured for a small team takes about 30–60 minutes if you know what decisions to make upfront. By the end of this tutorial, you'll have a shared hosting environment with team-level access controls, at least one site live under the right account structure, and staging set up so no one accidentally breaks production.

What You Need Before You Start

Skipping this step is how teams waste an hour backtracking. Run through the table below before touching any settings.

A note on plans: GrowBig supports multiple websites and is the realistic starting point for any team managing more than one domain. If you're comparing plans or weighing SiteGround against other options entirely, the SiteGround vs. alternatives comparison breaks down where it wins and where it doesn't.

What You'll Have When You're Done

When this tutorial is complete, your SiteGround setup will be in this exact state:

• One account owner with full billing and admin access
• Team members added as collaborators with defined, limited permissions
• Each site (up to five) installed under its own separate space in Site Tools
• Staging environments created and linked to production for every active site
• Daily automatic backups confirmed and at least one manual backup tested
• SSL active on all domains
• DNS pointed correctly, or flagged as pending if domain propagation is still in progress

That's a functional, team-ready setup — not just a single site with one login. The goal here is a configuration that holds up when two or three people are working across different sites at the same time, without stepping on each other or needing to share a single admin password.

Launch Your Website with SiteGround

Steps 1–3: Getting SiteGround Set Up for Your Small Team

Before you touch any settings, it helps to know what you're actually deciding here. Setting up SiteGround for a small team isn't just about getting a site online — it's about choosing an account structure that won't create headaches when a second person needs access, or when you're managing site three and suddenly can't remember which login owns what. These first three steps shape everything that follows.

Step 1: Choose the Right Hosting Plan for 1–5 Sites

The plan you pick determines how many websites you can host, how much server space you're working with, and whether you'll need to upgrade in six months. SiteGround offers three shared hosting tiers: StartUp, GrowBig, and GoGeek.

What to do:

• If you're managing a single site, StartUp works fine to begin.
• For two or more sites, you need GrowBig at minimum — StartUp only allows one website.
• GoGeek adds staging environments and more server resources, which matters once your team is making frequent changes to live sites.
• Cloud hosting is available too, but it's sized for higher traffic and heavier resource demands — skip it for now unless you already know you need it.

Why it matters:

Most small teams underestimate how quickly "one website" becomes three. You add a client project, a partner's site, or a staging copy — and suddenly you've outgrown a plan you just paid for. Picking GrowBig upfront costs a little more but saves a painful mid-year migration. The on-site pricing at SiteGround's checkout reflects introductory rates, so check renewal pricing before committing.

How to verify:

After completing your purchase, log into your Site Tools dashboard. Under your account overview, you'll see the active plan name and how many websites are allowed. If the number matches what you need, you're clear to move forward.

Step 2: Add Your First Website and Configure the Basics

Once the account is live, you'll land in SiteGround's User Area. From here, you can add a new website — either by registering a domain through SiteGround or by connecting one you already own elsewhere.

What to do:

• In the User Area, click Add New Website .
• Choose whether you're using a new domain (SiteGround can register it), an existing domain, or a temporary domain while you sort out DNS.
• For existing domains, select "existing domain" and enter it — you'll update the nameservers at your registrar later.
• After adding the domain, SiteGround walks you through selecting a data center. Pick the one closest to your primary audience. This affects load speed in a real way, not a theoretical one.
• Choose whether to start with WordPress, WooCommerce, or another application — or skip and install manually later. For most small teams, the WordPress auto-install is the fastest path.

Why it matters:

The data center choice is permanent unless you migrate. If your audience is in Europe and you pick a US server, you'll notice the difference in load time. It's a one-time decision that's easy to get right and annoying to undo. The temporary domain option is genuinely useful if your client's site is still live elsewhere — you can build, test, and then cut over without any downtime during setup.

How to verify:

Go to My Websites in the User Area. Your new site should appear with a green status indicator. Click Site Tools to open the dashboard for that specific website. If Site Tools loads and shows your domain name at the top, the site has been added correctly. You don't need to wait for DNS to propagate at this point — that comes later.

For a broader look at how SiteGround handles multi-site management and whether it fits your workflow, the SiteGround review at Toolvoro covers real-use considerations worth reading before you scale.

Step 3: Set Up Team Access With Collaborators

This is the step most small teams skip, then regret. SiteGround's Collaborators feature lets you give team members access to specific websites without sharing your master account credentials. It's the right way to handle shared access — full stop.

What to do:

• Inside the User Area, navigate to Collaborators from the left-hand menu.
• Click Add New Collaborator .
• Enter the email address of the team member you're adding. They'll receive an invitation to create or link a SiteGround account.
• Choose their access level: you can grant full access to the account or limit them to specific websites only.
• For most small teams, limiting access to specific sites is the smarter setup. A developer working on site two doesn't need visibility into site one's settings or billing.
• Repeat the process for each person on your team.

Why it matters:

Sharing login credentials is a common workaround, but it creates two problems immediately. First, you lose any audit trail — if something breaks, you can't tell who changed what. Second, if someone leaves the team, you have to change your master password and update every tool and integration that uses it. Collaborator access avoids all of that. Each person has their own login, and you can revoke access for one person without disrupting anyone else.

The access controls here are straightforward rather than granular, so if you need role-based permissions at a very detailed level, it's worth weighing that against SiteGround's current toolset. For most teams of two to five people, the available controls are enough.

How to verify:

After sending invitations, go back to Collaborators and check the status column. Pending means the invite hasn't been accepted yet. Once a team member accepts, the status changes to Active. Ask them to log into their own SiteGround account and confirm they can see the assigned website in their dashboard. That confirmation takes thirty seconds and tells you the access chain is working correctly.

Where to go next:

Steps 4–6 cover DNS configuration, SSL setup, and email account creation — the parts that make the site actually usable. If you're still deciding whether SiteGround is the right fit for your team at all, the SiteGround vs. alternatives comparison at Toolvoro lays out how it stacks up on the factors that matter most for small teams.

Read the Full SiteGround Setup Tutorial

Step 4: Add Team Members and Assign Roles

Once your hosting account is live and your first site is installed, the next thing to sort out is access. This is where small teams often get sloppy—someone shares the master login, everyone works from the same credentials, and you lose all visibility into who changed what.

SiteGround handles this through its Collaborators feature inside Site Tools. It lets you invite people to specific sites without giving them access to your entire hosting account or billing panel.

How to do it:

• Log in to your SiteGround Client Area and open Site Tools for the relevant website.
• Navigate to My Collaboration in the left sidebar under the user icon or account section.
• Click Add Collaborator , enter the email address of your team member, and select a permission level.
• Send the invitation. The collaborator gets an email prompting them to create or connect their SiteGround account.

Permission levels matter here. A developer needs access to tools like File Manager, MySQL, and FTP. A content editor probably only needs WordPress access—not the hosting panel at all. Be intentional. If someone only manages copy or uploads images, set them up directly in WordPress with an Editor role instead of making them a SiteGround collaborator.

Why this matters:

Shared logins are a liability. If a contractor leaves, there's no clean way to revoke access when everyone's using the same password. Collaborator accounts solve that—you remove them from Site Tools and they're out, immediately, without changing credentials that affect everyone else.

How to verify it's working:

• Ask the collaborator to log in and confirm they can see only the sites you intended.
• Check that they cannot access billing, subscription details, or other websites on your account.
• Confirm their permission level by having them attempt an action outside their scope—it should be blocked.

If you're managing multiple websites across a small team, document who has access to what. A shared spreadsheet works fine. You don't need a ticketing system; you just need clarity. Teams running more complex permission structures across several sites may also want to read through the SiteGround review for a deeper look at how collaborator features compare to other hosts.

Step 5: Configure Backups and Verify They're Actually Running

Backups are one of those things that feel optional until the moment they're not. SiteGround includes automated daily backups on most plans, but there are two problems teams run into: they assume backups are running without checking, and they don't know how to restore when something breaks.

Fix both of those now, before anything goes wrong.

How to do it:

• In Site Tools, go to Security → Backups .
• Check the backup schedule shown. On GrowBig and GoGeek plans, daily backups are included. On StartUp, you get daily backups too, but restoration options and on-demand backups may be more limited depending on your plan tier.
• To create a manual backup right now, click Create Backup . Label it something descriptive like "pre-plugin-update" so you know exactly what state it captures.
• Scroll through the list of existing backups to confirm dates are current and consecutive—gaps in the schedule are a warning sign.

Run a test restore:

This step is non-negotiable. A backup that's never been tested is just an assumption.

• Select a recent backup from the list.
• Click Restore and choose a staging environment or a non-critical file path if available on your plan.
• Confirm the restored version loads correctly and matches what you expect.

If you're on a plan without staging, do a partial test—restore a single file or database table rather than the full site. It's not perfect, but it confirms the backup files are intact and readable.

Why this matters:

A plugin update, a bad code edit, or a malware injection can take a site down in minutes. For a small team without a dedicated sysadmin, getting back to a known-good state quickly is the difference between a 10-minute fix and a half-day crisis. SiteGround's one-click restore is genuinely fast—but only if you've verified it works before you actually need it.

How to verify the setup is solid:

• Confirm at least seven recent daily backups appear in the backup list.
• Make sure at least one manual backup exists labeled with a meaningful description.
• Document the restore process somewhere your whole team can find it—a shared doc, a pinned Slack message, wherever your team actually looks.

If you're thinking about automating more of your backup and maintenance workflow, the SiteGround automation strategy covers practical approaches that work well at small-team scale.

Step 6: Set Up Staging and Establish a Deployment Workflow

This is the step most small teams skip because it feels like overhead. It isn't. A staging environment is how you stop testing changes on a live website—which, at some point, will break something in front of actual users.

SiteGround includes a staging tool on GrowBig and GoGeek plans. If you're on StartUp, you'll need to either upgrade or use a plugin like WP Staging to get similar functionality.

How to set up staging in Site Tools:

• Go to WordPress → Staging in Site Tools.
• Click Create Staging Copy . SiteGround clones your live site to a temporary subdomain.
• Wait for the clone to complete—this usually takes a few minutes depending on site size.
• Note the staging URL and confirm the site loads correctly there.

The staging site is a full copy: same files, same database, same plugins and settings. Changes you make there have zero effect on the live site until you explicitly push them.

Build a simple deployment workflow:

You don't need a CI/CD pipeline. For a team of two to five people managing a few websites, a lightweight process is enough—as long as everyone follows it.

A workable pattern looks like this:

• All theme edits, plugin updates, and new feature builds happen on staging first.
• Before pushing to live, one other team member reviews the change on staging and confirms it looks right.
• Changes are pushed using the Push to Live button in Site Tools, which replaces the live site with the staged version.
• After pushing, someone verifies the live site loads correctly and spot-checks the changed area.

That four-step process catches most problems before users see them. It also creates a natural checkpoint that prevents one person from accidentally shipping a half-finished change to a client's site.

A few things to watch:

• Staging and live sites share the same media library in some configurations—changes to media files may appear in both. Check your setup before assuming full isolation.
• If you push staging to live, the live site's database is overwritten. Any content added to the live site after you created the staging copy will be lost. Time your pushes accordingly, or create a fresh backup of live immediately before pushing.
• Team members who aren't familiar with staging should be briefed on this workflow explicitly. It only takes one person making edits directly on live to undermine the whole setup.

How to verify everything is working:

• Make a small, visible change on staging—a text edit on the homepage works fine.
• Confirm that change does not appear on the live site.
• Push staging to live and confirm the change now appears there.
• Check that no unintended content was lost in the push.

For teams still deciding whether SiteGround's staging and collaboration tools fit their specific setup, the SiteGround vs. alternatives comparison is a practical place to weigh the options before committing further.

See the Full SiteGround Setup Guide

Troubleshooting: When the Setup Doesn't Go Smoothly

Even a straightforward SiteGround setup can hit snags. Most issues small teams run into fall into a handful of predictable categories — and almost all of them have a fix that takes under ten minutes once you know where to look.

SSL Certificate Not Activating

This is the most common complaint after a fresh install. You've pointed your domain, installed WordPress, and the padlock still isn't showing. A few things could be happening.

First, check propagation. DNS changes can take anywhere from a few minutes to 48 hours. SiteGround's Site Tools dashboard includes a propagation checker — use it before assuming something is broken.

If propagation is complete and SSL still isn't active:

• Go to Site Tools → Security → SSL Manager
• Check whether an SSL certificate is assigned to the correct domain (including the www version)
• If it shows "Let's Encrypt" as pending, hit the refresh icon and wait two to three minutes
• Make sure your domain isn't still pointing to a previous host's nameservers

One thing teams miss constantly: having both the root domain and the www variant covered. SiteGround will let you install SSL on one without the other, which causes mixed-content warnings and a broken padlock even when the cert technically exists.

WordPress Login Loops or White Screen After Install

This usually happens when a plugin or theme conflicts with SiteGround's built-in caching layer (SG Optimizer). The fix is almost always the same.

• Access your site via Site Tools → WordPress → Staging and test there first if possible
• If you can't log in at all, go to Site Tools → File Manager , navigate to wp-content/plugins, and rename the plugins folder to plugins_disabled
• This deactivates all plugins without requiring admin access
• Log in, then rename the folder back and reactivate plugins one at a time

White screens with no error message are often a memory limit issue. SiteGround sets reasonable defaults, but some themes and page builders push past them. Add define('WP_MEMORY_LIMIT', '256M'); to your wp-config.php file via File Manager or SSH if you have access.

Collaborator Access Not Working Correctly

If you've added a team member through SiteGround's Collaborators feature and they can't see the right tools — or can't log in at all — here's what to check:

• Confirm the invite was accepted (pending invites don't grant access)
• Verify the permission level assigned matches what they actually need; "Viewer" access won't let someone push files or manage DNS
• Have the collaborator clear their browser cache and try a private window before assuming the account is broken
• Check whether they're logging into the correct SiteGround account if your team manages multiple client sites under separate accounts

One thing worth knowing: SiteGround's collaborator roles don't map to WordPress user roles. A collaborator with full Site Tools access still needs a separate WordPress admin account to manage content inside the CMS. These are two different systems and keeping them separate is intentional — but it confuses teams who aren't expecting it.

Email Not Sending or Landing in Spam

SiteGround includes email hosting, but getting it to work reliably for transactional email (password resets, contact forms, order confirmations) requires a bit more setup than most teams expect.

• Go to Site Tools → Email → Accounts and confirm the email address actually exists on the server
• For WordPress contact forms and WooCommerce, install a dedicated SMTP plugin like WP Mail SMTP and configure it to use SiteGround's outgoing mail server
• SiteGround's outgoing SMTP settings are in Site Tools → Email → Accounts → More → SMTP credentials
• Make sure SPF and DKIM records are published in your DNS — SiteGround adds these automatically if you're using their nameservers, but if you've pointed DNS elsewhere you'll need to add them manually

If emails are going to spam, the problem is almost never SiteGround's fault directly. Check your domain's SPF record using a tool like MXToolbox. A missing or malformed record is the culprit more often than not.

Staging Site Changes Not Pushing to Live

SiteGround's staging environment is genuinely useful, but the push-to-live process has a few quirks that catch teams off guard.

• You can push files, the database, or both — but the default doesn't always push everything you expect
• If you made changes to both content and theme files, make sure you select the full push option rather than a partial one
• After pushing, clear SiteGround's cache immediately via SG Optimizer → Purge Cache (or the cache icon in the WordPress toolbar)
• If the live site still looks wrong after clearing cache, check whether your browser is serving a cached version — force-refresh with Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac)

One common mistake: making changes to the live site while also working in staging. When you push staging to live, those live changes get overwritten. Set a clear rule with your team — edits happen in staging only until a push is confirmed.

Validation Checks Before You Call Setup Done

Running through a quick checklist before handing access to the rest of your team saves a lot of back-and-forth later. These aren't optional polish items — they're the things that cause real problems if skipped.

DNS and SSL

• Both root domain and www resolve to the site without redirects or security warnings
• SSL certificate shows as active and assigned to both variants in SSL Manager
• HTTPS redirect is enabled so HTTP requests automatically forward

WordPress Core

• WordPress is updated to the current stable release
• Default plugins (Hello Dolly, Akismet if not in use) are removed
• Admin username isn't "admin" — change it if it is
• A non-admin editor or author account is set up for day-to-day content work

Performance

• SG Optimizer is installed and caching is enabled
• At least one page speed test has been run (SiteGround's built-in tool or Google PageSpeed Insights) and scores are reasonable for your site type
• Images are compressed before upload or an optimization plugin is active

Backups

• Automatic daily backups are confirmed active in Site Tools → Security → Backups
• A manual backup has been triggered and confirmed as restorable — don't assume the system works until you've verified one restore

Team Access

• All collaborators have accepted their invites and can log into Site Tools
• Each team member has the correct WordPress user role for their responsibilities
• No one is using the primary account holder's login credentials

When to Contact SiteGround Support

SiteGround's support is genuinely responsive for a shared and cloud hosting provider. For small teams without a dedicated sysadmin, it's worth knowing when to use it rather than spending an hour debugging alone.

Reach out to support when:

• DNS propagation has completed but SSL still won't activate after trying the steps above
• A server-side error (500, 503) persists after plugin deactivation and cache clearing
• Email deliverability problems persist after SPF and DKIM records are verified
• You've lost access to the account and need identity verification to regain it

Don't wait on support for things that are documented clearly in Site Tools — WordPress updates, cache clearing, and adding collaborators are all self-serve and faster to do yourself.

For broader strategy around what to automate and what to handle manually, the SiteGround automation strategy guide covers how small teams can reduce repetitive admin work over time. And if you're still deciding whether SiteGround is the right fit before committing to a full setup, the SiteGround review and SiteGround vs. alternatives comparison are worth reading alongside this tutorial.

Launch Your Website with SiteGround

Did It Work? Run These Checks Before You Go Live

Setup feels done before it actually is. Run through these binary checks first — each one has a clear yes or no answer, and none of them require guesswork.

Objective checks:

• Your domain resolves in a browser without a security warning
• HTTPS is active and the padlock shows in the address bar
• WordPress (or your chosen CMS) loads the admin dashboard without errors
• At least one non-admin team account can log in successfully
• File Manager or SFTP access works for anyone who needs it
• Your staging environment is separate from the live site
• Automated daily backups are enabled and show a recent restore point
• Contact forms or any transactional email routes through a verified sender domain
• Plugin and theme updates are not set to auto-deploy directly to production

If any of these return a "no," stop. Fix that item before you touch anything else. A missed backup config or a broken team login will cause problems at the worst possible moment.

Ready to Go Live? The Honest Readiness Check

Objective checks tell you whether the setup works. This section tells you whether your team is genuinely ready to hand a live site to real visitors.

These are judgment calls, not binary pass/fail items.

Ask your team these before flipping the switch:

• Does everyone who needs site access know their login and understand their role permissions?
• Is there a shared document — even a simple one — that explains where backups live and how to restore from one?
• Has at least one person reviewed the staging site on mobile and a second browser?
• Do you have a point of contact for SiteGround support, and does your plan include priority support or just ticket-based?
• If something breaks at 11 PM, does someone on the team know what to do first?

Small teams often skip the last two. That's fine until it isn't. SiteGround's support is genuinely responsive, but you still need someone internally who knows the difference between a plugin conflict and a server issue.

One more thing worth confirming: your DNS TTL. If you migrated a domain, lower TTL values (300–600 seconds) propagate changes faster. If you set it high before migration, check whether it has fully propagated using a tool like whatsmydns.net before you announce the site publicly.

3 Toolvoro Pro Tips

Pro Tip 1: Use SiteGround's Collaborator Role Instead of Sharing Credentials

Sharing one login across a team is a security and audit nightmare. SiteGround's Site Tools includes a Collaborators feature that lets you add team members with defined access scopes. Each person gets their own login. If someone leaves, you remove their access without changing a master password. For teams managing two or more sites, this alone is worth setting up on day one — not day fifteen.

*Pro Tip 2: Set Up Staging Before You Need It*

Most teams create a staging environment after something breaks. That's backwards. SiteGround makes one-click staging available inside Site Tools, and it takes about two minutes to configure. Do it during initial setup. Then make it a team rule: no plugin updates, theme changes, or new integrations go straight to production. Test on staging, confirm it works, then push. This one habit prevents the majority of small-team site disasters.

Pro Tip 3: Connect Your Email Notifications to One Shared Inbox

SiteGround sends backup confirmations, security alerts, and uptime notifications to the account owner's email by default. If that's a personal address, the whole team is blind to critical events. Create a shared team inbox — even a simple Google Group works — and route all SiteGround notifications there. Pair that with a basic automation to flag urgent keywords like "backup failed" or "downtime." For more on building those kinds of workflows, see the SiteGround automation strategy guide.

Frequently Asked Questions

How many team members can access one SiteGround account?

SiteGround doesn't publish a hard cap on collaborator accounts for standard plans. In practice, small teams managing one to five sites can add the team members they need through the Collaborators feature in Site Tools. Each site can have its own set of collaborators, which keeps permissions clean when different people manage different projects.

Do I need a separate SiteGround plan for each website?

No. SiteGround's GrowBig and GoGeek plans support multiple websites under one account. If your team manages five sites, you don't need five plans — you need a plan with enough resources and the right storage allocation. Check the current plan details on SiteGround's site directly, since resource limits change. For a side-by-side view of how SiteGround stacks up against other multi-site options, the SiteGround vs alternatives comparison breaks it down clearly.

What happens if a team member accidentally breaks the live site?

SiteGround's automated daily backups give you a restore point, but there's a gap between when something breaks and when you notice. That's why staging matters. A broken staging site is recoverable in seconds. A broken live site with no recent backup is a much harder conversation. The setup recommendation above — staging before you need it — directly addresses this.

Can SiteGround handle a small e-commerce team's workflow?

For teams running WooCommerce or light Shopify-adjacent setups through WordPress, yes. SiteGround's performance layer (SuperCacher, PHP version controls, CDN) handles standard small-store traffic without configuration headaches. What it won't do is replace a dedicated e-commerce platform for high-volume operations. If you're in that range, the SiteGround review has a more detailed breakdown of where performance holds up and where it doesn't.

Is SiteGround support available 24/7 for small plans?

Yes, SiteGround offers 24/7 support across all paid plans, including live chat. Response times and support depth vary by plan tier. Teams managing revenue-generating sites should look closely at whether their plan includes priority support — it affects how fast you get a human when something goes wrong on a Sunday night.

What's the biggest setup mistake small teams make?

Rushing DNS. Teams migrate a domain, see the site load in their browser (which may still be pulling from cache or local DNS), assume everything is fine, and announce the launch. Then visitors on different networks hit the old server for another 24–48 hours. Verify propagation externally before you go public.

What to Do Next

If you've cleared the objective checks and your team is confident in the readiness questions, you're set. Don't over-engineer the setup — small teams don't need enterprise-level configuration. A clean install, proper role permissions, staging enabled, backups confirmed, and email alerts routed correctly is genuinely enough to operate reliably.

If you want to understand how the tool works at a deeper level before committing to a workflow, start with the full SiteGround tutorial for step-by-step guidance on the setup itself. Already using SiteGround and wondering whether it's still the right fit for where your team is heading? The best SiteGround alternatives page gives you an honest look at what else is worth considering.

Start Your SiteGround Setup

Read the Full SiteGround Review

See SiteGround Plans & Pricing