⚙ Organization Configuration
Fine-tune your organization's general settings, notification preferences, assignment defaults, and payment gateway integrations.
General Settings
General settings control the core behavior of your organization. These are configured during initial setup but can be modified at any time by an Organization Admin.
| Setting | Description | Default |
|---|---|---|
| Organization Name | The display name shown in the dashboard, emails, and reports | Set during creation |
| Timezone | IANA timezone used for all date/time displays and scheduling | UTC |
| Currency | Currency code for monetary values (COD, payments, reports) | EGP |
| Logo | Organization logo displayed across the platform | Deliverty default logo |
| Active Status | Whether the organization is active and operational | true |
Only users with the settings.update permission (or Organization Admin / Super Admin roles) can modify organization settings. Users with settings.read can view but not change them.
Notification Preferences
Configure how and when notifications are sent to customers, agents, and administrators. Deliverty Hub uses Novu as its notification infrastructure, supporting multiple channels.
Available Channels
| Channel | Description | Recipients |
|---|---|---|
| In-App | Real-time notifications in the dashboard and mobile app via WebSocket | Admins, Agents, Customers |
| Email notifications for important status changes | Admins, Customers | |
| Push | Mobile push notifications via the Deliverty Driver App | Agents |
| SMS | Text messages for critical delivery updates | Customers |
Notification Events
The following table shows which notifications are sent for each task status change and to which recipient type:
| Event | Customer | Agent | Admin |
|---|---|---|---|
| CREATED | In-App, Email | — | In-App, Email |
| ASSIGNED | — | In-App, Push | In-App |
| ACCEPTED | In-App, Email | — | In-App |
| IN_TRANSIT | In-App, Email, SMS | — | In-App |
| COMPLETED | In-App, Email, SMS | In-App, Push | In-App, Email |
| CANCELLED | In-App, Email | In-App, Push | In-App, Email |
In-app notifications are delivered in real-time via WebSocket connections. Both the dashboard (<Inbox /> component) and the mobile app (NovuProvider) receive updates instantly without polling.
Assignment Defaults
Configure default assignment behavior for your organization. These settings determine how newly created tasks are assigned to agents.
| Setting | Description | Default |
|---|---|---|
| Assignment Mode | Whether tasks are assigned automatically or manually by dispatchers | manual |
| Default Algorithm | The algorithm used for automatic assignment (see Algorithms) | nearest |
| Max Search Radius | Maximum distance (in meters) to search for available agents | 10000 (10 km) |
| Auto-Retry | Whether to automatically retry assignment if an agent rejects the task | true |
Each organization can have only one active assignment configuration at a time. You can create multiple configurations but only one can be marked as active. See How Assignment Works for the full flow.
Payment Gateway Setup
Deliverty Hub supports integrating payment gateways for online payment collection. Configure your gateway credentials to enable customers to pay for deliveries electronically.
Supported Payment Methods
| Method | Description | Status |
|---|---|---|
| Cash on Delivery (COD) | Agent collects payment from the customer at the delivery location | Built-in |
| Online Payment | Customer pays via payment gateway before or after delivery | Configurable |
| Prepaid | Payment already collected by the merchant before task creation | Built-in |
Gateway Configuration Steps
Choose a Payment Provider
Select your payment gateway provider from the supported list in Settings → Payments.
Enter API Credentials
Provide your gateway API key, secret key, and any additional configuration parameters required by the provider.
Test the Connection
Use the "Test Connection" button to verify that your credentials are valid and the gateway is reachable.
Enable Online Payments
Once verified, toggle online payments on. Customers will see the online payment option when applicable.
Payment gateway credentials are encrypted at rest and never exposed in API responses. Only users with the settings.update permission can view or modify payment gateway configuration. Always use production keys only in production environments.
Next Steps
- Configure assignment rules to automate task distribution
- Add agents to your fleet
- Learn more about payments and COD management
- Explore notification workflows in detail