Instance configuration

This documentation outlines the essential and elective steps required for an administrator to set up and maintain a Notyfire instance. These configurations are managed under the ADMINISTRATION section of the sidebar navigation.

To perform the following steps use must have 2 roles assigned: admin and manager. For details see: Overview.

Obligatory Configuration

These sections must be configured to establish the foundational data structure of the platform.

• Organisation Structure: Administrators must define the company's hierarchy to ensure announcements and users are correctly categorised.

  • Departments: Define high-level business or technical units, such as IT Operations, Software Development.

  • Teams: Create specific working groups (e.g. DevOps) and link them to their respective departments.

• Systems: Systems represent the infrastructure and external tooling you also want to include in your communication.

  • Services: Define internal resources that may require status updates, such as VPN or WiFi.

  • Tools: Add any tools used by the organisation, including Argo CD, Jira, Bitbucket, Artifactory, Jenkins or Confluence.

• Applications: This section maps the software landscape that Notyfire will track.

  • Applications: Register the primary software stacks developed in the company.

  • Components: For each application, define its sub-elements (e.g. frontend and backend) to allow for granular deployment tracking.

• Users: User management varies depending on your organisation's authentication setup:

  • Login/pass: If SSO (Single Sign-On) is not configured, administrators must manually add users via the "add new" button or by using the "Import" functionality to upload a CSV file.

  • SSO: If SSO is active, user accounts are automatically created during first login, inheriting attributes from the identity provider.

    • User Attributes: Each record tracks the First Name, Last name and Email. Roles are assigning in Notyfire.

Optional Configuration

These sections enhance the automation and consistency of the platform but are not strictly required for basic functionality.

• Global Subscriptions: Global subscriptions automate the notification process for large groups of users based on their professional profiles.

  • Filters: Create criteria-based filters such as CI/CD, PM tools, or Office facilities.

  • Profiles: Define roles (e.g., Developer, Office worker) and link them to specific Attributes (e.g., development or office work).

  • Mapping: Link filters to profiles so that any user with a matching attribute automatically receives relevant notifications.

• Announcement Templates: To ensure standardised and rapid communication during critical events, administrators can pre-configure templates.

  • Consistency: Templates pre-fill the announcement fields, allowing publishers to disseminate information quickly without limited manual formatting. Usefull for keeping standardication (common examples: Incidents, Maintenance or App Launch)

Advanced Instance Settings

Under the Configuration tab, administrators can manage global system behaviours:

• Integrations