Tenant Setup Tutorial

This tutorial guides platform administrators and implementation leads through provisioning a production-ready EGKits tenant. You will create the tenant shell, configure identity and modules, import starter master data, and run a go-live checklist.

#Scenario

Gulf Services Co. is onboarding to EGKits SaaS V10 for finance, sales, and HR operations across two branches. The IT lead must stand up the tenant, delegate admin access, and confirm module readiness before user training begins.

#Prerequisites

#Step 1 — Register and activate the tenant

1. Navigate to Signup and select Start Trial or Create Organization.
2. Enter organization name, admin email, and preferred region (affects data residency defaults).
3. Choose default language (English, Arabic, or bilingual) and currency.
4. Confirm your email via the activation link sent to the admin inbox.
5. Sign in at your tenant URL (for example https://yourorg.egkits.com or your custom domain).
6. Complete the first-run wizard: company address, fiscal year start, and time zone.

Tip: Use a distribution list (for example admin@company.com) only if your mail policy allows shared MFA devices. Prefer a named owner account for audit clarity.

#Step 2 — Configure company and fiscal foundation

1. Open Administration > Company Profile and enter legal entity details.
2. Add branch or site records under Administration > Branches if operating multi-location.
3. Navigate to Finance > General Ledger > Fiscal Calendar and confirm the active year.
4. Open the current Fiscal Period and verify status is Open for operational modules.
5. Set default Tax jurisdiction and seed tax codes appropriate to your country.
6. Upload company logo and document templates under Administration > Branding (optional but recommended before user invitations).

#Step 3 — Enable modules for phase 1

1. Go to Administration > Modules.
2. Enable core modules first:

3. Enable industry or extended modules (HR, Hospitality, Fixed Assets) according to your rollout plan.
4. Disable modules not licensed to avoid menu clutter and permission noise.
5. Save and refresh the Apps menu to confirm only enabled modules appear.

#Step 4 — Design roles and invite administrators

1. Open Administration > Roles and review seeded roles (Admin, Accountant, Sales, Viewer).
2. Clone Admin to create a scoped role such as Finance Admin if segregation of duties is required.
3. Assign permissions at module level — prefer least privilege for non-admin users.
4. Navigate to Administration > Users > Invite User.
5. Invite at least two administrators for continuity:

6. Ask invitees to accept email invitations and enroll MFA before production data entry.

#Step 5 — Configure integrations and mail

1. Open Administration > System Configuration > Email and configure SMTP or provider API keys.
2. Send a Test Email to confirm notification delivery for invites and approvals.
3. If using API integrations, create service accounts under Administration > API Keys with scoped permissions.
4. Configure webhooks or external ERP connectors if applicable (see Sync Errors guide).
5. Set session timeout and password policy under Administration > Security Policies.

#Step 6 — Import starter master data

1. Download CSV templates from Administration > Data Import.
2. Prepare and validate files offline:

3. Run imports in order: COA → trading partners → products → opening balances.
4. Review import logs for rejected rows and correct source data before re-importing.
5. Spot-check imported records in each module UI.

#Step 7 — Run the go-live validation checklist

1. Sign in as a non-admin test user and confirm menu visibility matches role design.
2. Create a test sales invoice and verify GL posting (use a test customer or rollback in sandbox).
3. Confirm audit trail entries appear under Analytics > Audit Trail.
4. Verify backup and retention settings with your platform administrator or host operator.
5. Document tenant URL, admin contacts, and module list in your internal runbook.

#Expected results

#Troubleshooting

#Related links

• Onboarding Guide — structured onboarding playbook
• Multitenancy Guide — isolation and database topologies
• Identity & Access Guide — RBAC design patterns
• System Configuration Guide — tenant-wide settings
• Security Best Practices — hardening checklist
• Core Concepts — platform architecture overview