Configure sandbox or production environment
Choose the environment label used by module settings and operational review.
Exact navigationAdmin Area → EmaraTax eInvoicing → Settings → Environment
Before you begin
- Use the exact navigation above and confirm the intended record, tenant, customer, property, document or date range.
- Confirm module activation and the stated permission instead of using another staff member’s account.
- For public, email, provider, finance, signature or destructive actions, use a controlled test record before production use.
What this guide covers
Choose the environment label used by module settings and operational review. These instructions follow the supplied module’s live menus, controller actions, form fields, model validation and downstream effects.
Exact step-by-step process
- Sign in to the staff admin area and open Admin Area → EmaraTax eInvoicing → Settings → Environment.
- Confirm that your account meets the access rule: Administrator.
- Open the required record or configuration and review its current values before making a change.
- Complete the displayed fields or action exactly as described in this guide.
- Save, submit, download or confirm the action using the button presented by the module.
- Reopen the source record and verify the expected status, output, notification, file or linked record.
Fields, choices and supported possibilities
ChoicesSandbox or Production
DefaultSandbox
Category/help-centre/category/emaratax-einvoicing/
Topic/help-centre/topic/emaratax-einvoicing-production-asp/
Code-backed validations and workflow rules
- Selecting Production does not create an accredited ASP submission capability.
- Production use requires independent ASP onboarding, endpoint authentication and final regulatory testing.
Expected result and verification
- The configure sandbox or production environment workflow completes without bypassing the module’s permission and validation checks.
- The saved value, generated file, status, notification or linked CRM record is visible from the same workspace.
- Any validation message remains visible until the source data or setting is corrected.
Security, privacy and operational checks
- Use least-privilege staff access and do not use another person’s account to reach a hidden action.
- Review personal, financial, identity and compliance data before sending, exporting or exposing it through a public link.
- Test configuration, email, public forms, accounting effects and provider connections with controlled records before production-wide use.