Back to SankaLogin

Admin Onboarding Checklist

Use this first-day checklist to set up a workspace, invite users, load initial data, and avoid rework.

Guide overview

This checklist is for workspace admins who are preparing a new team, business unit, or rollout. It is designed to reduce repetitive setup questions and prevent avoidable rework during the first week.

Align the workspace basics

Before inviting the whole team, confirm the settings that affect every record:
  1. Review the modules your team needs first.
  2. Confirm the workspace timezone, currency, and date display rules.
  3. Decide which objects will be the source of truth for companies, items, locations, orders, and billing records.
This prevents teams from creating duplicate master data in different places.

Invite users and assign roles

Start with a small admin group, then expand to operational users.
  1. Invite the core admins who will own setup and approvals.
  2. Add staff users only after you know which objects they should view or edit.
  3. Review view-only, staff, and admin permissions before launch.
Recommended practice:
  • Keep a short list of workspace admins.
  • Give edit rights only to teams that maintain the master data.

Configure the operating rules

After the workspace basics are ready, standardize how users will work inside the app.
  1. Create the core properties your team needs for reporting and automation.
  2. Prepare saved views for daily work, exception handling, and audit checks.
  3. Set search scope and filter templates for the lists people use every day.
  4. Decide who owns records such as orders, purchase orders, invoices, or tasks.
If these rules are clear early, users ask fewer “where should I enter this?” questions later.

Load initial data in the right order

A clean import order prevents broken links between records.Recommended sequence:
  1. Companies and contacts
  2. Items
  3. Locations
  4. Inventory or opening stock
  5. Open operational records such as orders, purchase orders, invoices, or tasks
If you use CSV, test with a small sample file before importing the full dataset.

Run a dry run before launch

Before inviting the wider team, walk through one complete business flow with real admins.Examples:
  • Create one customer and one item
  • Receive stock into a location
  • Create an order or purchase order
  • Confirm whether the right users can see, edit, and search the records
Use the dry run to catch missing permissions, missing properties, and unclear views before your team depends on the workspace every day.
PreviousGet Started with SankaNextBasic Concepts of Sanka