Setup checklist
Prepare the tenant in a deliberate order. A new owner account is not evidence that financial, stock or Care operations are ready.
Information to collect
| Item | Example | Why it matters |
|---|---|---|
| Confirmed tenant code and name | BHS / Bright Home Supplies | Prevent changes in the wrong business |
| Verified owner contact | Sara, approved business email | Operator setup and recovery use a private link |
| Entitled capabilities | PARTY, ORGANIZATION, SALES and dependencies | Subscription eligibility precedes enablement |
| Operating structure | HQ with North and South branches | Scope should follow actual responsibility |
| Job access requirements | Farah: receipt entry, posting and allocation at North | Build a reviewed role rather than granting every permission |
| Approval record | Internal access request BHS-ACCESS-014 | Recommended review evidence; no implied application approval queue |
Recommended sequence
- Have the operator provision the tenant and first owner if they do not already exist.
- Complete the owner's setup link and sign in through the normal tenant login.
- Confirm platform entitlements, then configure required tenant modules and features.
- Create the business-unit structure and check identity/contact information.
- Create ordinary job roles and assign their complete intended permission sets.
- Create staff users and assign roles.
- Assign business-unit access and one selected primary unit.
- Ask each user to sign in freshly and perform an approved acceptance check.
- Complete module-specific setup, including accounts and numbering where required.
Acceptance checks
Use both an allowed example and a refused example. For Farah, confirm the intended North workflow is available, then confirm she cannot operate on a South record. Test against approved training records; do not post a real invoice merely to prove a menu works.
Keep a second authorised recovery contact available before restricting an administrator. SUPER_ADMIN identity changes and ownership replacement belong to the operator workflow. Do not attempt an owner transfer by editing role membership.
If setup stops at one layer, resolve that layer before adding broader permissions. For example, a missing subscription entitlement requires the operator; adding another role cannot supply it.