Organization setup
Setting up your organization, business units and the foundational records each module depends on.
- Audience
- Administrators, Implementation partners
- Permissions needed
- Platform administration, Organization settings
- Prerequisites
- A platform administrator account
- Environment
- Production and staging
- Product version
- Current
- Last reviewed
- Owner
- Propulsive Product Team
Before you start
- Do this before inviting general users - most modules' setup wizards assume your organization and business units already exist.
Organization setup is the first thing an administrator does on a new deployment - it establishes the structure that every module’s own setup wizard then builds on.
Organization and business units
Under Organization, you define your company’s structure and, if relevant, separate Business Units (useful if you run more than one brand, location or legal entity through the same deployment). Accounting’s chart of accounts, fiscal calendar and cost centres are scoped against this structure, so it’s worth getting right before Accounting setup.
Per-module setup wizards
Once your organization exists, go through each module’s setup wizard in roughly this order:
- Roles & permissions - who can do what, before anyone else is invited.
- Inventory - units of measure, item categories, warehouses (many other modules reference these).
- Accounting - chart of accounts, fiscal calendar, business units, tax codes.
- Sales / Procurement / HR / CRM - each has its own wizard for rate cards, vendor terms, salary structure, pipeline stages and so on.
Each wizard is a live-computed checklist, not a one-time form - it recalculates progress from your actual data, so you can return to it any time to see what’s still outstanding. A step can also be manually marked complete by an administrator if it was configured a different way.
What “seed data” means here today
A module’s setup wizard walks you through creating the foundational records it needs - it does not silently populate your deployment with data you didn’t ask for. A formal, versioned system for promoting starter/reference data between environments is defined in our internal standards but isn’t fully implemented yet - see Deployment & Onboarding for where that stands.