Appearance
Multi-Tenancy
Pinkapple ERP is a multi-tenant platform. Each company that registers gets a fully isolated environment with its own database, configuration, and user base.
System Reference
| Area | How Users Interact With It | What It Controls |
|---|---|---|
| Company Registration | Public company registration page | Creates the tenant context, company alias, initial service, and initial administrator setup. |
| Login And Service Selection | Login and context-selection screens | Places the user inside the correct company, service, and business unit context. |
| Business Units And Types | Administration -> General Setup -> Business Units And Types | Defines tenant-visible hierarchy and service scoping. |
| Users And Roles | Administration -> Access | Controls who can enter the tenant and what each user can see or do. |
How It Works
Database-Per-Tenant Isolation
When you register a company on Pinkapple, the system creates:
- A dedicated database for your company's data
- A unique company alias (URL-friendly identifier) used in all your URLs
- Default configuration — service, business unit hierarchy, admin role, and fiscal calendar
Your data never mixes with another company's data. Each tenant database contains its own:
- Chart of accounts
- Client records
- Financial transactions
- User accounts and roles
- GL journals and sub-ledgers
- Configuration settings
Company Alias
Your company alias is derived from your company name during registration and identifies your company context when users sign in.
For example, if your company is "Acme Financial Services", your alias might be acme-financial-services, and users would use the company-specific login context provided during onboarding.
INFO
The company alias is permanent and cannot be changed after registration. Choose carefully during the registration process.
What's Shared Across Tenants
While data is fully isolated, certain platform-level resources are shared:
| Shared | Isolated Per Tenant |
|---|---|
| Service definitions & profiles | Service subscriptions |
| Permission definitions | Role assignments |
| Application code & UI | Configuration settings |
| — | Users & credentials |
| — | Chart of accounts |
| — | GL posting rules |
| — | Clients & accounts |
Security
- Data isolation — Your company's data is completely separate from other tenants
- Request scoping — Every API request is authenticated and scoped to your company
- Audit logging — All data mutations are logged with user and timestamp
Next Steps
- Navigation & Permissions — How the UI adapts to your role and service context
- Getting Started — Register your company and log in