Settings

• 1: Preferences
• 2: Manage Organization
• 2.1: General Options
• 2.2: Notifications
• 2.3: Billing Details
• 2.4: Licenses
• 2.5: Payment History
• 2.6: Members
• 2.7: Logo and Branding

1 - Preferences

2 - Manage Organization

The Manage Organization page is where organization owners configure org-level settings, membership, billing, and branding. Access to this page is restricted to organization owners and administrators; non-admin users can view fewer options or receive an access denied message.

Left-hand tabs

• General: edit the organization name and display name
• Notifications: configure global notification channels
• Billing Details: enter or update billing contact, billing address, and tax information used on invoices.
• Licenses: view current license counts and usage, purchase additional seats, or renew expiring licenses.
• Payment History: review past invoices, payments, and subscription activity.
• Members: invite, remove, or change roles for organization members; manage pending invitations and role-based permissions.
• Customize: upload organization logo and set branding options shown in the UI and on shared reports.

2.1 - General Options

Organization name and display name

• Display Name: a human-friendly name shown in the UI and reports.
• Actual Name: a machine-safe identifier used by tooling (ConfigWizard, ConfigWizardCmd, agents). The actual name is sanitized to remove or replace characters that could break scripts or client tools; avoid spaces and punctuation when choosing an organization name.

Default instance settings

• “Acknowledge you are running jobs as a sysadmin”: when checked, new instances registered in this organization will have the same acknowledgement enabled by default. This setting simply controls the default for newly added instances and can be changed per-instance later.

Organization key

• Regenerate organization key: use this to replace the org key if it is lost or compromised. Regenerating the key immediately invalidates the current key — all existing agents and integrations using the old key will stop communicating and must be reconfigured with the new key. Confirm this action only after planning for agent reconfiguration.

Delete organization

• Delete organization: permanently removes the organization and all org- scoped data. This action is irreversible and requires explicit confirmation (type-to-confirm). Only organization owners can perform deletion.

2.2 - Notifications

This page configures how your organization receives alerts from QMonitor. Use these settings to deliver operational notifications to the right channels and reduce noise by choosing appropriate delivery methods per severity.

From the Notification settings page you can enable one or more channels and test each configuration before saving.

Supported notification channels

QMonitor currently supports the following notification channels:

• Email
• Microsoft Teams
• Telegram
• Slack

Each channel can be enabled independently and tested using the Test button available next to the configuration fields.

Email notifications

1. Enable Email
2. Enter one or more email addresses (use commas to separate multiple recipients)
3. Click Test to verify delivery
4. Save the configuration

Microsoft Teams notifications

QMonitor sends notifications to Microsoft Teams using an Incoming Webhook URL. Messages are delivered to a specific channel as Adaptive Cards and may include text and images (graphs associated with issues).

How to enable

1. In Microsoft Teams, open the target Team and Channel
2. Click More options next to the channel name
3. Select Workflows
4. Create a new Incoming Webhook
5. Copy the generated Webhook URL
6. Paste it into QMonitor → Teams webhook url
7. Click Test to verify delivery
8. Save the configuration

If you do not have access to the Workflows section contact your Teams administrator

Telegram notifications

Telegram notifications are sent by a Telegram bot to a channel.

Step-by-step setup

1. Create the bot

1. Open Telegram and search for @BotFather
2. Send:

   /newbot
   

3. Choose a name and a username

BotFather will return a Bot Token like:

123456:ABC-defGHI...

This value goes into Bot token in QMonitor.

2. Create a Telegram channel

1. Telegram → New Channel
2. Choose a name
3. Set it as Private (recommended)
4. Create the channel

3. Add the bot as administrator

1. Open the channel → Info → Administrators
2. Add your bot (e.g. @thenameyouchooseearlier)
3. (Mandatory) Grant at least “Can post messages” permission

4. Retrieve the Channel Chat ID

1. Send any message in the channel
2. Open in a browser:

   https://api.telegram.org/bot<YOUR_BOT_TOKEN>/getUpdates
   

3. Look for the chat section in the JSON response:

"chat": {
  "id": -1003314549127,
  "title": "ChannelName",
  "type": "channel"
}

The Chat ID is the negative number (e.g. -1003314549127).

Final parameters to enter in QMonitor

• Bot token → Telegram bot token
• Chat ID → Channel chat ID

After saving, use Test to confirm delivery.

Slack notifications

Slack notifications support:

• Text messages via Incoming Webhooks
• Images (optional) via Slack Bot API

1. Create a Slack App

1. Go to https://api.slack.com/apps
2. Click Create New App → From scratch
3. Choose a name (e.g. QMonitor)
4. Select the workspace

2. Enable Incoming Webhooks (required)

1. Features → Incoming Webhooks
2. Activate Incoming Webhooks → ON
3. Add New Webhook to Workspace
4. Select the target channel
5. Copy the Webhook URL

This value goes into Slack Incoming Webhook URL.

3. Enable image upload (optional)

Required only if you want to also see the notification’s associated images (graphs contained in issues).

Add the following bot scopes in OAuth & Permissions:

• chat:write
• files:write
• channels:read
• groups:read (only for private channels)

After adding scopes, reinstall the app.

4. Retrieve Bot Token

Copy the Bot User OAuth Token (xoxb-…).

This value goes into Slack Bot token.

5. Retrieve Channel ID

Open Slack in the browser and navigate to the channel.

URL example:

https://app.slack.com/client/TXXXXXXX/CYYYYYYY

Use CYYYYYYY (public) or GYYYYYYY (private).

This value goes into Slack Channel ID.

6. Invite the bot to the channel

Inside the Slack channel, run:

/invite @QMonitor

Without this step, image uploads will not be visible.

Final parameters to enter in QMonitor

• Webhook URL → required
• Bot token → required only for images
• Channel ID → required only for images

Use Test to confirm correct delivery.

2.3 - Billing Details

Billing information form

• The Billing info section is a form where you enter your company’s billing details used to generate invoices. Typical fields include company name, billing address, VAT number / fiscal code, contact name, email, and phone.
• Changing the country in the form will show or hide additional country- specific fields. For example, selecting Italy exposes “Certified Email Address (PEC)” and “SDI Code” fields required on Italian invoices.
• The information you provide here is printed on invoices. Keep it accurate to avoid delays or invoice re-issues.

Purchase prerequisites and VAT rules

• You must complete the billing form before purchasing licenses; the system will block checkout until required billing fields are provided.
• EU reverse-charge VAT: if your company is in an EU country, reverse-charge treatment applies only when you supply the required identifiers (for example VAT Number and/or national fiscal code as applicable). If you do not provide the necessary information, VAT will be applied to the license price and included on the invoice.

Sanctions and restricted sales

• We cannot sell licenses to entities or individuals located in countries sanctioned by the European Union or the Italian Republic. This includes, but is not limited to, Russia, Iran, and Afghanistan.
• If your billing address or company registration is in a sanctioned jurisdiction, purchases will be declined.

Tips and support

• Use official company identifiers (VAT or fiscal codes) to ensure correct tax treatment and avoid invoice corrections.
• If you need assistance completing country-specific fields, contact your finance team or open a support ticket via the Help menu.

2.4 - Licenses

The Licenses page lists all available licenses and provides actions to renew or manage them.

License list

• Columns shown for each license:
  • Valid to: the license expiry date.
  • Name: a friendly name or a GUID that identifies the license.
  • Assigned to: the SQL instance the license is assigned to; blank if not assigned.
• Each row has a checkbox so you can select one or more licenses for bulk actions.

Renewal and payment

• Use the “Renew # licenses” button to proceed to the payment page and renew the selected licenses.
• Payment is processed by Stripe; QMonitor does not store payment methods or credit card numbers.

Actions and notes

• Select multiple rows to renew licenses in bulk.
• Assigned/unassigned status is shown in the table; use the button at the top of the list to assign licenses

Assign vacant licenses

• When you have multiple licenses available, use the “Assign licenses” button to automatically allocate vacant licenses to instances that do not currently have a license. The assignment process selects unassigned licenses and binds them to unlicensed instances until either all selected licenses are used or all instances are licensed.

2.5 - Payment History

The Payment History page lists all payments and invoices for the organization. Use this view to review past charges, download invoices, and reconcile billing.

Payments table

• Columns:
  • Date: payment or invoice date.
  • Paid: amount actually paid (currency).
  • Total: invoice total before/after taxes as shown on the invoice.
  • Invoice: link to the invoice document (PDF).

Actions and filters

• Click an Invoice link to download or open the invoice PDF for accounting.

Notes

• Payment method and transaction details are recorded with each entry.
• For billing questions or disputes, contact billing support

2.6 - Members

This page lets organization owners manage access and invitations.

Access and invitations

• Initially only organization owners can access the Manage Organization pages.
• Owners can invite new users with the “Invite” button at the top-right.
• The invite dialog lets you enter an email address or copy an invitation code to share directly. The dialog shows the code immediately for manual distribution.
• The invited user receives an email with the invitation link and code. If the user is not registered, they must sign up first and then redeem the invitation code or follow the link to join the organization.

Members list

• The members table shows current organization users with simple controls:
  • Email: the member’s email address.
  • Role: a dropdown to change the member role (Owner or User).
  • Delete: remove the member from the organization.
• Role changes and removals may require confirmation.

Behavior and tips

• Use Owner role sparingly; owners can manage billing, policies, and members.
• Prefer inviting users to a role of “User” and elevate to Owner only when necessary.
• Invitations expire after a limited time; resend if a user reports an expired invite.

2.7 - Logo and Branding

Organization logo

• Current logo: the page displays the organization’s current logo for both themes so you can verify what users see.
• Theme-specific logos: you can upload a separate logo for Light and Dark themes to ensure good contrast and legibility in both modes.
• Upload controls: choose a file for the Light logo and a file for the Dark logo. Supported formats: PNG and SVG. Recommended dimensions: provide a high-resolution square or horizontal asset; SVGs scale crisply for all sizes.

Preview and reset

• Preview: the preview area shows how the selected logos and accent color will appear in the UI before you save changes.
• Reset: click Reset to revert the logo for the current theme back to the product default. Reset does not affect the other theme’s logo unless you reset it as well.