Services

In Pinkapple ERP, a service is a bundled collection of modules that your company subscribes to. Services determine which features, permissions, and data domains are available to your users.

A service context does not mean every module inside it owns separate copies of shared primitives. Agriculture, Manufacturing, Billing, POS, Driving, and other services can change the navigation and business language, but shared primitives such as Inventory, Inspections, Payments, Reporting, Resource Capacity, Documents, and GL should still remain single sources of truth where applicable.

Workspace Reference

Workspace	How Users Reach It	What Users Usually Do There
Service Selector	Login or context-selection flow where multiple contexts are available	Choose the service and business unit context before entering the application.
Service Switcher	Main application sidebar	Switch between accessible services or business units after login.
Business Units And Types	Administration -> General Setup -> Business Units And Types	Maintain the service-specific hierarchy that scopes roles and records.
Users And Roles	Administration -> Access	Assign users to service-linked business units and grant service-filtered permissions.
Service-Specific Workspaces	Sidebar modules such as Loans, Production, Agriculture, Billing, POS, or Accounting	Perform operational work in the active service context without duplicating shared primitive ledgers.

What Is a Service?

A service represents a distinct business offering or product line on the Pinkapple platform. Each service comes with a set of service profiles that group related permissions together.

For example, a "Banking & Finance" service might include profiles for:

Profile	Modules Included
ACCOUNTING	Chart of accounts, GL journals, reconciliation
FINANCE	Fiscal setup, currency, exchange rates, budgets, pricing
LOANS	Loan products, applications, accounts, repayments
CRM	Client management, groups, deposit accounts
GENERAL	Dashboard, user management, configurations
REPORTS	Report catalog, report builder, financial statements
COMMUNICATIONS	Documents, messages, templates
HR	Employee management, payroll, leave, attendance
SECURITY	Roles, approval levels, approval configurations
BILLING	Accounts payable, accounts receivable
COMPLIANCE	Audit trails, regulatory compliance

Service Profiles Control Permissions

When an administrator creates a role for users, the available permissions are filtered by the service profiles attached to that role's business unit type. This means:

• A role in a "Banking & Finance" service will never see INVENTORY permissions
• A role in a "Community Finance & HR" service will see a different set of available permissions

TIP

Service profiles are configured at the platform level by Pinkapple administrators. As a tenant administrator, you select which service your company uses during onboarding or by contacting support.

Multiple Services

A single company can subscribe to multiple services. Each service:

• Has its own business unit type hierarchy (see Business Units)
• Has its own root business unit type (the top-level type in the hierarchy)
• Scopes data independently — a chart of accounts in Service A is separate from Service B
• Has its own roles, GL code templates, and posting rules

Service Switching

If your company has multiple services, users who are assigned to business units in more than one service can switch between them using the Service Switcher in the sidebar.

The Service Switcher displays:

• All business units the user has access to, grouped by business unit type
• A search bar (when there are more than 5 business units)
• A count badge showing the total number of available business units

When you switch services, the sidebar navigation, available data, and active business unit all update to reflect the selected service context.

That switch can change:

• labels and menu groupings
• which modules are visible
• which business unit and permission scope is active

It should not change the architectural rule that shared primitives stay shared. A service may narrow context or add source workflows, but it should not silently create a second stock, inspection, payment, resource, reporting, or document ledger.

Default Services

When you register a new company, Pinkapple creates a default service with a standard set of profiles. The exact service depends on the company type selected during registration.

Common default services include:

Service	Target Audience	Key Profiles
Banking & Finance	Banks, MFIs	ACCOUNTING, FINANCE, LOANS, CRM, HR, REPORTS
Community Finance & HR	SACCOs, cooperatives	ACCOUNTING, FINANCE, LOANS, CRM, HR, REPORTS (excludes INVENTORY, INVESTMENTS)
Enterprise Finance	SMEs, corporates	ACCOUNTING, FINANCE, BILLING, HR, REPORTS

Manufacturing Service And Industry Categories

The Manufacturing service is the generic production service. It provides the shared Production runtime used by manufacturers across different industries.

Manufacturing should be configured with:

Layer	Purpose
Manufacturing Service	Tenant service scope for production, inventory, inspections, documents, costing, and reporting.
Production Foundation	Required shared setup for product designs, BOMs, routings, production orders, WIP, QC, and MRP.
Industry Categories	Optional or required overlays such as Apparel/Garments, Food Processing, Automotive, Roofing, Plastics/Rubber, or Metals.
Category Seed Packs	Templates, terminology, inspection plans, labels, document presets, dashboards, and reports.

Industry categories do not create separate services. A garment manufacturer should normally receive the Manufacturing service, Production permissions, and the Apparel/Garments category pack. The category pack can add school-uniform templates, size/color terminology, apparel QC checks, and label presets while users continue to work from Production, Inventory, Inspections, Billing, and Reporting.

See Manufacturing Industry Categories And Examples for a practical school-uniform manufacturing walkthrough.

How Services Relate to Other Concepts

Company
├── Service A (e.g., Banking & Finance)
│   ├── Business Unit Type: SERVICE_ROOT
│   │   └── Business Unit Type: DEFAULT_TYPE
│   │       ├── Business Unit: Head Office
│   │       └── Business Unit: Branch 1
│   ├── Roles (scoped to BU types in this service)
│   ├── Chart of Accounts (scoped to BU types in this service)
│   └── GL Posting Rules (scoped to BU types in this service)
│
└── Service B (e.g., Community Finance & HR)
    ├── Business Unit Type: SERVICE_ROOT
    │   └── Business Unit Type: DEFAULT_TYPE
    │       └── Business Unit: Kanama Office
    ├── Roles (scoped to BU types in this service)
    ├── Chart of Accounts (independent from Service A)
    └── GL Posting Rules (independent from Service A)

INFO

Most companies operate with a single service. Multi-service configurations are typically used by organisations that run fundamentally different business lines (e.g., a bank that also operates a cooperative savings arm).

Next Steps

• Business Units — Understand how business units and types create your organisational hierarchy within a service
• Navigation & Permissions — How services affect what you see in the sidebar