Skip to main content
You manage your tenant’s connections, schemas, saved runs, automations, and results — and the boundary is clear: users, permissions, and platform settings are outside your scope. A Tenant Admin manages the setup records and reconciliation workflows for one active tenant. The role can edit tenant-owned settings, connections, schemas, saved runs, automations, and results for the active tenant. Tenant Admins do not manage Darpan users, tenant membership, permission assignments, AI provider settings, global settings, or platform diagnostics. The steps below follow the order that matters: confirm the active tenant context first, then build setup records, then run and review.

​
Daily operating path

1

Confirm the active tenant

Open Ask Darpan with Cmd/Ctrl+K or the floating Ask Darpan button. Search for Open User Settings.In Tenant Context, confirm the active tenant before changing setup records or running reconciliation. If you have access to more than one tenant, select the tenant you want to manage.
2

Review tenant settings

Search for Open Tenant Settings. Confirm the tenant timezone and the registered Google Chat spaces.Use Manage tenant settings when the timezone or the chat-space registry needs to change.
3

Confirm reusable connections

Create or update the connection records the tenant uses:
  • Open SFTP Servers for file transfer.
  • Open NetSuite Settings for NetSuite access.
  • Open Shopify Settings and Open HotWax Settings for API-backed order reconciliation.
Use active records with clear names so runs and automations stay identifiable later.
4

Maintain schemas and saved runs

Use Create Schema or Open Schema Library when source file structure changes.Use Create Reconciliation Flow for a new saved run setup. Use Open Runs Settings when an existing saved run needs source, schema, primary ID, or rule changes.
5

Execute and review

Use Run Reconciliation for a controlled manual run. After the run completes, search by run name or output file name and open Open Result: ….Classify differences as source data, schema selection, rule behavior, or expected business variance before changing the setup.
6

Automate stable runs

Use Open Automations after the saved run and source setup are stable. Create manual or scheduled automations only after a manual run proves the setup returns useful output.

​
Tenant Admin checklist

  • Active tenant is correct before setup changes.
  • Timezone reflects the tenant’s operating context.
  • Run-completion notifications are configured when the team needs alerts.
  • SFTP, NetSuite, Shopify, and HotWax records use clear tenant-specific names.
  • Schemas match the current source files or API payloads.
  • Saved run names identify the two systems being compared.
  • Automations have a clear schedule, input mode, and history after testing.
  • Result review produces a next action: fix source data, adjust schema, change rules, rerun, or accept the variance.

​
When to ask a Super Admin

Ask a Super Admin to create users, assign tenant access, change role permissions, change platform settings, or investigate private operational diagnostics. Ask a Darpan admin (the DARPAN_ADMIN group) to configure AI providers.