Environment and access model

Production, staging, and sandbox are not interchangeable. Each environment exists to support a different kind of decision, and admins should keep validation, rollout, and recovery work moving through that sequence instead of improvising directly in production.

Use the section on Environment boundaries as the decision frame. The learner should explain when it matters, who owns the decision, what state they would inspect first, and how that state supports the lesson objective: distinguish the purpose of production, staging, and sandbox environments.

Evidence should come from role state, tenant context, audit history, release notes, governed setup pages, or the control plane being reviewed. For Environment boundaries, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

Access belongs to a business role in a specific tenant and environment. Admin work is not only provisioning; it also includes review, justification, expiry, and clean revocation when responsibilities change.

Turn the section on Access lifecycle discipline into a realistic example. Ask the learner to describe the situation they are responding to, the first surface they would open, the cue they expect to find, and what they would do if that cue is missing.

For Access lifecycle discipline, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

The administration overview tab should summarize platform state before an admin changes anything. Tenants, plans, users, and roles control who exists in the system and what each organisation is allowed to do. Audit verifies who changed what, and settings control tenant-level system behaviour.

Admins should treat each administration tab as a different control surface rather than as one generic setup page. That separation makes escalation, review, and rollback much clearer during support and rollout work.

Use this section to confirm the learner understands more than the page label. They should connect Administration workspace map to the business state, owner, and consequence behind it.

Geo Master is the governed source for countries, states, and cities. Admins should understand that those tabs affect address quality, regional logic, and downstream compliance behavior across the ERP, so countries, states, and cities cannot be treated as disposable lookup rows.

Master Upload is the bulk change surface for controlled master-data import. Admins should require template discipline, preview review, and explicit go or no-go checks before importing products, customers, vendors, employees, or other supported masters into a live tenant.

Use this section to confirm the learner understands more than the page label. They should connect Reference data and bulk import controls to the business state, owner, and consequence behind it.

Company Profile is the canonical source for the business name, address, GSTIN, logo, and bank details that appear on generated ERP documents. Admins should update that page deliberately because invoice and document output inherits those fields immediately.

Print Templates is the controlled layout surface for those documents. Treat template changes as governed rollout work: preview them against real company-profile data, confirm the right identity and settlement details render, and avoid casual edits that change customer-facing paperwork without review.

For Document identity and print governance, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

The Agentic ERP workspace is an operational control plane, not just a dashboard. Admins should know what each tab governs: dashboard for current agent state, history for prior runs, signals and alerts for emerging conditions, approvals for queued decisions, configuration and tools for operating boundaries, policies for guardrails, and metrics for control effectiveness.

The AI workspace and Barcode workspace also carry governed surfaces. Assistant approvals should only be available to reviewers who can validate operational consequences, while barcode generate, batch QR, batch barcode, scan, labels, and OCR should be treated as controlled workflow tools that can change how real-world execution is encoded and verified.

Use this section to confirm the learner understands more than the page label. They should connect AI, agent, and scanning control surfaces to the business state, owner, and consequence behind it.

Run the lesson as an admin control review. Start with the practical task: distinguish the purpose of production, staging, and sandbox environments. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from role state, tenant context, audit history, release notes, governed setup pages, or the control plane being reviewed. The practice should end with the learner connecting the action back to the lesson summary: teach admins to treat environments, identities, administration tabs, governed master-data surfaces, AI and agent control planes, and role boundaries as one operating model before any rollout or support change.

Close the exercise by asking the learner to restate the objective in operational terms: distinguish the purpose of production, staging, and sandbox environments. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not treat admin work as generic setup. Every permission, release note, template, automation, or master-data change should have an owner and a rollback or review path. In this lesson, watch for that risk while learners work on this objective: distinguish the purpose of production, staging, and sandbox environments.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain which environment should be used for validation versus live execution and describe why the lesson matters in real work.

Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot explain which environment should be used for validation versus live execution, keep the lesson in practice mode before marking it complete.