Getting Started

This guide gives administrators a production-oriented path for bringing a team onto Qwibik One.

Before you begin

Confirm the operating model for the organization:

• The legal or operating entity that owns the workspace.
• The first administrators and their responsibility boundaries.
• The modules that should be enabled at launch.
• Billing ownership and payment approval flow.
• Data import, integration, and support requirements.

Create the workspace

The workspace is the primary tenant boundary for Qwibik One. It defines where users, records, configuration, billing state, and product modules are scoped.

const workspace = await provisionWorkspace({
  name: "Acme Operations",
  region: "global",
  ownerEmail: "admin@example.com",
  modules: ["crm", "billing", "support"],
});

Invite the initial team

Start with a small administrator group. Assign roles deliberately, then expand access after the workspace structure is validated.

Validate launch readiness

Before the workspace is opened broadly, verify these areas:

1. Workspace profile and regional settings are correct.
2. Billing contact and plan state are confirmed.
3. User roles match the organization's operating model.
4. Support escalation paths are documented.
5. Initial integrations are tested in a controlled workflow.

Next steps

Continue with Workspaces for tenant architecture and Billing for plan and payment concepts.