Skip to main content

Client Onboarding Guide

Step-by-step guide for onboarding a new client to the Studio B / AcuOps platform.

Prerequisites​

Before starting, confirm:

  • Client has Acumatica Cloud or on-premise (version 24.1+)
  • Admin access to create API user
  • Client's Acumatica URL and tenant name
  • GitHub org invitation accepted
  • Railway project access granted

Phase 1: Infrastructure Setup​

1.1 Create Client Repository​

gh repo create studio-b-ai/studiob-{client}-acumatica \
  --template studio-b-ai/studiob-client-template --private

The template includes 55 files covering CI/CD, monitoring, and sync configuration.

1.2 Configure Client Settings​

Edit client-config.yaml in the new repo:

client:
  name: "Client Name"
  slug: "client-slug"
  erp:
    platform: acumatica  # or netsuite
    url: "https://client.acumatica.com"
    version: "24.200.001"
    tenant: "ClientTenant"

1.3 Set Up API User​

In the client's Acumatica instance:

  1. Navigate to SM201010 (Users)
  2. Create api-bot user with required roles
  3. Store credentials as GitHub secrets and Railway env vars

Phase 2: Monitoring Setup​

2.1 Deploy Health Probes​

Health probes monitor:

  • Acumatica API availability
  • Session auth success
  • Entity accessibility
  • Custom field registrations

2.2 Configure Slack Alerts​

Set up a dedicated Slack channel (e.g., #client-alerts) and configure the webhook URL.

2.3 Enable Schema Drift Detection​

Add the client's entities to the drift detector. Default monitored entities:

  • SalesOrder, Customer, StockItem, PurchaseOrder, Invoice, Shipment, Vendor

Phase 3: Customization CI/CD​

3.1 Export Existing Customizations​

Have the client export their customization project:

  1. Open SM204505 → Select project → Source Control → Save to Folder
  2. Commit to Customization/_project/ in their CI/CD repo

3.2 First Deploy​

Push to main to trigger the first automated deploy. Verify:

  • XML validation passes
  • Import succeeds
  • Publish completes
  • Schema verification confirms custom fields

Phase 4: Integration Setup (Optional)​

4.1 HubSpot Sync​

If the client uses HubSpot:

  1. Create HubSpot PAT with required scopes
  2. Create custom properties for sync fields
  3. Configure sync worker in webhook-router
  4. Verify bi-directional sync cycle

4.2 EDI (Orderful)​

If the client needs retailer EDI:

  1. Set up Orderful account
  2. Activate trading partners
  3. Configure EDI worker mappings

Verification Checklist​

  • API user can authenticate and query entities
  • Health probes all pass
  • Schema drift detector baselined
  • Customization deploy pipeline tested
  • Slack alerts configured and tested
  • Client team has access to monitoring dashboard