Instance Management
Installation-wide settings: the license, the organizations on it, and the channels PersivX delivers through.
License
| Field | Meaning |
|---|---|
| Expiry Date | When the current license stops being valid. |
| Max RAM usage allowed | The memory ceiling, in MB, for the whole installation. |
Both values are displayed read-only. Changing either requires a new license file — they cannot be extended by editing the database.
Organizations
One installation can host several organizations. The table lists each one with:
| Column | Meaning |
|---|---|
| Name | The organization's name. |
| # Developer Licenses | Developer licenses allotted to that organization. |
| # Viewer Licenses | Viewer licenses allotted to that organization. |
| Admin | The organization's administrator. Click to reassign it to another user. |
The per-organization license counts here are the limits the Users screen counts against.
Communication Channels
A communication channel is a configured route for PersivX to send through — used by subscriptions and alerts. The table lists the channel type, its name, and whether it is public.
Adding a Channel
Click Add Channel and give it a Name, decide whether it is Public, and choose what to Send via:
| Field | Notes |
|---|---|
| Server | Office 365 (Microsoft) or G-Mail (Google). |
| SMTP Sender Email | The address messages are sent from. |
| SMTP Port | Defaults to 587. |
| SMTP Password | Password for the sending account. |
| SMTP Tenant ID / Client ID / Client Secret | Used when sending through an email API rather than plain SMTP. |
Webhook
A URL that PersivX calls once per recipient when the channel is used.
| Field | Notes |
|---|---|
| Method | GET (the default), or POST, which sends a JSON body. |
| URL | The address to call. |
| Timeout | Seconds to wait for a reply. Leave it blank to use the server's default, which is half a second. That is too short for most messaging APIs, so set it for those. |
| Body | POST only. The JSON sent with each call. The channel won't save unless it is valid JSON. |
The URL and body can both use the placeholders listed under Webhook Delivery: <PERSIVX_CONTACT>, <PERSIVX_REPORT_NAME>, <PERSIVX_CUSTOM_CONTENT> and the rest. In a POST body, they are filled in inside the JSON values, so a message containing quotes or line breaks still sends correctly. When a body value is only a placeholder, as in "items": "<PERSIVX_CUSTOM_CONTENT>", and what it is filled with is a JSON array or object, that JSON is inserted as-is rather than as text. This lets a visual column supply a whole list, such as a messaging template's parameters. A POST call counts as delivered on any 2xx response. A GET call needs exactly 200.
Editing a Channel
Click the pencil icon on a channel's row to open it with its current settings. You can change everything except Send via: a channel's type is fixed once it is created, because subscriptions only offer channels of their own type. Subscriptions and alerts that use the channel pick up the change on their next run.
Saved passwords are never shown again. SMTP Password and SMTP Client Secret open empty; leave them empty to keep the saved value, or type a new one to replace it.
Public vs. Private Channels
- A public channel is available to everyone in the organization.
- A private channel can be shared with specific users — the share icon appears only on private channels.
Get DB Dump
The Get DB Dump action in the header downloads an installation-wide database dump — useful for backup and for migrating an instance.