Organization Setup Checklist
Establish a safe CapitalOS organization foundation before teams begin daily product and operations work.
Before you begin
Use an organization owner or administrator account and confirm that the organization is the intended workspace. Gather the team’s required modules, member responsibilities, external systems, product identifiers, financial assumptions, and communication needs before changing shared settings.
How it works
Organization setup is a sequence rather than a single form. General organization details establish context; Members, Roles, and Modules establish access; integrations supply supported external data; module settings define shared classifications and calculations; and imports or manual entry establish the first records.
The best order minimizes rework: define identity and access before loading data, then validate one small workflow before expanding use.
Step-by-step
- Review the organization’s general name and identifying information.
- Confirm the initial owners and administrators, then invite only the members needed for setup.
- Review or create roles and assign the least access required for each responsibility.
- Enable the modules included in the organization’s operating workflow.
- Configure shared module settings such as categories, columns, return classifications, or transaction fees where applicable.
- Connect only the external services needed now and allow supported synchronization to establish its initial state.
- Confirm the SKU convention and how parent and child variations will be represented.
- Add or import a small sample of organization data and resolve validation or matching issues.
- Walk one product through the relevant workflow and verify linked records in Products or Orders.
- Configure alerts, email behavior, and collaboration settings only after their prerequisites are working.
- Invite remaining team members and validate their actual access.
Check your result
Members have appropriate roles, required modules appear, integrations show a usable state, and a controlled sample record can move through the intended workflow. The organization has a consistent SKU approach and administrators know which shared settings influence calculations or classifications.
Common problems
Too many settings appear at once: prioritize identity, access, modules, and one end-to-end workflow. Optional refinements can follow after the foundation works.
Imported records do not match: check the SKU convention and workbook validation before importing a larger file.
An integration is connected but data is incomplete: initial synchronization, backfill, external permissions, and matching can take additional time or attention.
Members see different modules: compare their role assignments and the organization’s enabled modules.
Permissions and data notes
Many setup controls affect every organization member. Record the reason for access and calculation changes, review external account permissions, and avoid large imports until a sample passes validation. Danger Zone actions are deliberately outside this checklist.