Setting Up Your Organization on SAVHN: A Complete Implementation Manual

Who this manual is for

This manual is written for the person who will actually click the buttons: an IT lead, operations manager, or founder who has been handed the job of "get us set up on SAVHN." It assumes you have decided to use the platform and now need to take it from an empty organization to something your team can log into and start using. It does not cover choosing which modules to run long-term (see the Module Marketplace implementation manual for that) — it covers the foundation everything else sits on: the organization itself, the first admin account, basic branding, and your department structure.

SAVHN is multi-tenant software. Every customer operates inside an organization — a fully isolated workspace that owns its own users, records, permissions, and module configuration. Nothing you do here is visible to any other organization on the platform, and nothing from another organization leaks into yours. That isolation is the starting assumption for everything below.

Prerequisites

Before you begin, have these ready:

• A verified email address that will become the organization's primary administrator account. This should be a role-durable address (an IT or ops mailbox) rather than a single person's personal inbox, if you can arrange it — it's the account of last resort if something goes wrong later.
• Your organization's legal or trading name, industry, and primary time zone.
• A list of the departments or business units you want reflected in the system (Sales, Operations, Finance, Support, and so on). You don't need a perfect list — you can add, rename, or restructure departments after go-live — but arriving with a rough draft saves a step.
• A decision on which core modules you plan to use first. You are not locking anything in at this stage; you're only avoiding the trap of configuring an organization for modules you never enable.
• Your company logo file and brand color, if you want branding done in the same session. This step is optional and can be revisited later.

Step 1: Create the organization

From the sign-up flow, choose to create a new organization rather than joining an existing one via invite (invite-based joining is for team members added after the org already exists). Enter the organization's display name, industry, and country or region.

The industry selection matters more than it looks. SAVHN ships 22 built Industry Clouds, and the industry you select is used to recommend a relevant starting template — a set of modules and configuration defaults suited to how that kind of business actually runs. Picking the closest match, even if it isn't a perfect fit, gives you a better starting point than a completely generic setup. You can still enable or disable individual modules afterward regardless of which industry you picked.

Step 2: Complete the primary administrator account

The email address used to create the organization becomes the primary administrator. Complete that account fully before inviting anyone else — set a real password, confirm the email address, and fill in the administrator's name and role. This account will hold the highest level of permissions in the system by default, so treat its credentials with the same care you'd give any other master administrator login.

A common mistake here is creating the org under a named individual's personal account and then having that person leave the company eight months later, taking effective control of the primary admin login with them. If you can create a second admin account immediately (Step 6 covers this) or use a shared IT mailbox for the primary account, do it now rather than after it becomes a problem.

Step 3: Set your organization's basic branding

Branding in SAVHN is not cosmetic decoration — for organizations using the Client Portal module, your branding is what your own clients see when they log in to check on their projects, invoices, or tickets. Getting it right at setup avoids a second pass later.

At minimum, set:

1. Your organization display name (already set in Step 1, but confirm it renders correctly — abbreviations and punctuation sometimes need a second look).
2. Your logo, uploaded at a reasonable resolution so it doesn't look stretched or pixelated on both desktop and mobile views.
3. A primary brand color, used across dashboard accents and, where applicable, client-facing surfaces.

If you don't have final brand assets ready, it's fine to skip this step and return to it later — nothing else in the setup depends on branding being finished.

Step 4: Define your department structure

Departments are the organizational backbone that later steps build on: role assignments, reporting lines, and module access all reference departments. Go back to the rough list you prepared in the prerequisites and enter it as your initial department structure.

Keep the first pass simple. It is much easier to start with five clean departments and split one into two later than to start with fifteen granular departments and merge them once you realize half your team doesn't fit neatly into any of them. A department structure that roughly mirrors how your organization already thinks about itself — Sales, Operations, Finance, Support, whatever your actual functional groups are — will need the least rework down the line.

For each department, set:

• A clear name (avoid internal-only abbreviations that a new hire wouldn't recognize).
• A department lead, if you already know who that will be. This can be changed later and doesn't block anything if left blank for now.

Step 5: Set your working calendar and locale defaults

Confirm the organization-level time zone, and if your organization spans multiple locations or time zones, note that individual modules like HRMS and Projects allow location- or team-level overrides later. Getting the top-level default right now means fewer individual corrections needed as you bring on more users.

Step 6: Create a second administrator account

Before you invite the broader team, create at least one additional administrator account, distinct from the primary one created in Step 2. This is not bureaucratic caution — it is the difference between "the person who set this up is on vacation and nobody can reset a password" and a five-minute fix. Assign it to a real second person, not a placeholder.

Step 7: Run the pre-invite checklist

Before opening the door to the rest of your team, walk through this checklist:

Item	Status you want before inviting the team
Organization name, industry, and time zone	Set and confirmed correct
Primary administrator account	Fully activated, real password set
Second administrator account	Created and activated
Department structure	At least a first-pass structure entered
Branding (logo, brand color)	Set, or explicitly deferred with an owner assigned
Core modules for launch	Decided (even if not yet configured — see the Marketplace manual)

Once every row is either done or intentionally deferred with an owner, you're ready to move to role and permission configuration and then to inviting your team.

A realistic timeline for getting this done

Organizations tend to either rush this (and pay for it later in cleanup) or treat it as a multi-week project (and lose momentum before the team ever logs in). Neither extreme serves you well. A reasonable pace for a mid-sized organization looks like this:

Phase	Typical duration	What happens
Organization and admin account creation	Same day	Steps 1–2 above
Branding	1–3 days	Can run in parallel with department planning; not a blocker
Department structure	1–2 days	First-pass structure, refined later based on real usage
Second admin account and checklist	Same day	Should not be deferred past the first week
Team invitations	Following week	Once role-based permissions are configured (a separate implementation manual)

If your organization is larger or has more complex departmental or regulatory requirements, stretch this timeline accordingly — but resist letting "we'll get to branding eventually" turn into a six-week delay before anyone outside the founding admin account has logged in. Momentum matters more than perfection at this stage.

Why the foundation matters more than it looks

It's tempting to treat organization setup as throat-clearing before the "real" work of configuring modules and permissions. In practice, decisions made here — department names, the primary admin account structure, whether branding is finished before the Client Portal goes live — ripple through everything that follows. A department structure that doesn't match how the business actually operates makes every subsequent role assignment harder than it needs to be. A primary admin account tied to one person's personal inbox becomes a liability the day that person is unreachable. Getting the foundation right the first time is materially cheaper than fixing it after fifty users have already been onboarded around a flawed structure.

Common Pitfalls

Treating the industry selection as permanent. It only sets a starting template. If your business doesn't cleanly match any of the 22 Industry Clouds, pick the closest one and adjust module configuration afterward — don't spend time hunting for a perfect match that may not exist.

Building an overly granular department structure on day one. New organizations consistently over-engineer this step, creating a department for every sub-team that exists on an org chart. Start coarse; split departments later once real usage shows you where the lines should actually be.

Skipping the second administrator account. This is the single most common setup mistake, and the one most likely to cause a genuine emergency later — a locked-out primary admin with no backup means calling support to prove ownership of the organization.

Uploading a low-resolution logo. It looks fine on your own screen at setup time and then looks blurry the first time a client opens the Client Portal on a phone. Use the largest clean version of your logo you have.

Inviting the whole company before roles and permissions are configured. Everyone lands with default access until you configure role-based permissions, which means either over-exposure or a confusing "why can't I see anything" period. Do organization setup, then permissions, then the invite wave — in that order.

Frequently Asked Questions

Can we change the organization name or industry after setup?

Yes. The organization name can be updated at any time from organization settings. The industry selection can also be changed, though because it only affects the starting template it recommended at setup, changing it later doesn't retroactively alter modules you've already configured.

Do we need to finish branding before inviting the team?

No. Branding can be completed at any point, and updating it later doesn't disrupt anything already in progress. It matters most for organizations using the Client Portal module, since that's the surface your own clients see.

How many administrator accounts should we have?

At least two, from day one, held by two different real people. Beyond that, the right number depends on your organization's size — role-based permissions (covered in a separate implementation manual) let you grant administrative capability over specific modules without making everyone a full organization administrator.

What happens to our departments if we restructure the company later?

Departments can be renamed, merged, or split at any time. Role assignments and module access tied to a department follow the department, so a rename doesn't disrupt anyone's access — a merge or split is worth reviewing role assignments afterward to confirm they still make sense.

Getting started

Setting up the organization itself typically takes less than an hour of focused work — the steps above are the entire foundation everything else in SAVHN builds on. If you want to see the full setup flow before committing, SAVHN offers a 7-day free trial with no setup obligation. From there, use the pricing configurator to select the modules your organization actually needs, or contact the developer team directly if you'd rather talk through your specific structure before you start clicking.