Skip to main content
GIMA’s notification system keeps users informed about important events, maintenance schedules, asset changes, and system alerts. Configure notification preferences to ensure the right people receive the right information at the right time.

​
Overview

Access notification settings at /configuracion/notificaciones to configure alerts and email notifications.
Proper notification configuration ensures that maintenance staff, managers, and administrators stay informed about critical events without being overwhelmed by unnecessary alerts.

​
Notification Types

GIMA supports various types of notifications:

Maintenance Alerts

Notifications for scheduled maintenance, overdue tasks, and maintenance completions

Asset Changes

Alerts when assets are created, modified, moved, or retired

System Events

Critical system notifications, errors, and status updates

User Activity

Notifications about user actions, permission changes, and access events

​
Configuring Notifications

1

Access Notification Settings

Navigate to /configuracion/notificaciones from the configuration dashboard.
2

Select Notification Type

Choose which type of notification you want to configure (maintenance, asset, system, or user).
3

Set Delivery Preferences

Configure how and when notifications should be delivered:
  • Email notifications
  • In-app notifications
  • Mobile push notifications (if enabled)
4

Define Recipients

Specify who should receive these notifications:
  • Specific users
  • User roles or departments
  • Custom distribution lists
5

Save Configuration

Save your notification settings to activate them.

​
Email Notifications

​
Email Configuration

Configure SMTP settings for outgoing notifications:
  • SMTP server address
  • Port and encryption (SSL/TLS)
  • Authentication credentials
  • From address and display name
Customize email notification templates:
  • Subject lines
  • Body content and formatting
  • Include relevant asset or maintenance details
  • Add company branding and logos
Configure when emails are sent:
  • Immediate delivery for urgent alerts
  • Batched/digest emails for non-urgent notifications
  • Daily or weekly summary emails
  • Quiet hours to avoid after-hours notifications

​
Email Notification Examples

Asunto: Mantenimiento Programado - [Asset Name]

Un activo requiere mantenimiento programado:

Activo: [Asset Name]
ID: [Asset ID]
Ubicación: [Location]
Fecha programada: [Due Date]
Tipo de mantenimiento: [Maintenance Type]

Por favor, complete esta tarea antes de la fecha indicada.

Acceder al sistema: [Link]

​
In-App Notifications

In-app notifications appear in the GIMA interface:

​
Notification Bell

The bell icon in the top navigation bar shows:
  • Red dot indicator for unread notifications
  • Notification count badge
  • Click to open notification panel

​
Notification Panel

The notification panel displays:
  • List of recent notifications (most recent first)
  • Notification type icon
  • Brief message summary
  • Timestamp (relative time)
  • Mark as read/unread
  • Clear all option
Notifications are accessible via the bell icon in the dashboard header, located next to the user profile and search bar.

​
Notification Preferences by Event

​
Maintenance Events

Alert when maintenance is due soon:
  • Trigger: X days before scheduled date
  • Recipients: Assigned technicians, maintenance manager
  • Frequency: Daily reminder until completed
Alert when maintenance is past due:
  • Trigger: Day after due date
  • Recipients: Assigned technicians, supervisor, manager
  • Frequency: Daily until completed
  • Escalation: Notify higher management after X days
Notification when maintenance is finished:
  • Trigger: Task marked as complete
  • Recipients: Requester, manager, asset owner
  • Frequency: One-time notification

​
Asset Events

Notification when a new asset is added:
  • Trigger: Asset creation
  • Recipients: Asset managers, department heads
  • Details: Asset ID, category, location, value
Alert when an asset is moved:
  • Trigger: Location field updated
  • Recipients: Asset owner, location managers
  • Details: Old location, new location, moved by whom
Notification on status updates:
  • Trigger: Status field changed
  • Recipients: Relevant stakeholders based on new status
  • Details: Previous status, new status, reason for change

​
System Events

Critical error notifications:
  • Trigger: System error or failure
  • Recipients: System administrators
  • Priority: High (immediate notification)
Regular backup notifications:
  • Trigger: Scheduled backup completion or failure
  • Recipients: IT administrators
  • Frequency: Daily or per backup schedule
Security-related notifications:
  • Trigger: Unauthorized access, failed logins, security policy violations
  • Recipients: Security administrators, IT managers
  • Priority: High

​
User Activity Notifications

​
Permission Changes

Notify users when their permissions are modified:
  • Access granted to new modules
  • Permission levels changed
  • Access revoked

​
Account Events

Notify users about account-related events:
  • Password reset required
  • Account locked due to failed logins
  • Profile information updated

​
Notification Channels

Configure which channels are used for different notification types:
Event TypeEmailIn-AppMobilePriority
Critical Alerts✓✓✓High
Maintenance Due✓✓-Medium
Asset Changes-✓-Low
Daily Summaries✓--Low
System Status✓✓-Medium

​
Notification Rules

Create custom notification rules based on conditions:
1

Define Trigger

Specify what event triggers the notification (e.g., “Asset value exceeds $10,000”)
2

Set Conditions

Add conditions that must be met (e.g., “AND category is COMPUTO”)
3

Choose Recipients

Select who receives the notification
4

Select Channels

Decide which notification channels to use
5

Activate Rule

Enable the rule to start receiving notifications
Test notification rules thoroughly before activating them in production to avoid sending unnecessary alerts or missing critical notifications.

​
Notification Frequency Settings

​
Digest Options

Send notifications as soon as events occur:
  • Best for: Critical alerts, urgent maintenance
  • Risk: Can lead to notification fatigue
Combine multiple notifications into periodic batches:
  • Hourly: Send every hour if there are new notifications
  • Daily: Daily summary at specified time
  • Weekly: Weekly digest on specified day
Best for: Non-urgent updates, status reports
Suppress non-critical notifications during specified hours:
  • Set start and end time (e.g., 10:00 PM - 6:00 AM)
  • Define which notification types respect quiet hours
  • Critical alerts can override quiet hours

​
Best Practices

Avoid Alert Fatigue

Configure notifications carefully to avoid overwhelming users with too many alerts

Use Appropriate Channels

Send critical alerts via multiple channels; use email for non-urgent updates

Target the Right People

Ensure notifications go to users who can act on them

Test Configurations

Test notification settings before deploying to production

Regular Reviews

Periodically review and adjust notification settings

Clear Message Content

Use clear, actionable language in notification messages

​
Troubleshooting

Check:
  • Email server configuration is correct
  • User email address is valid and verified
  • Emails are not going to spam folder
  • Notification rule is enabled and conditions are met
  • User has email notifications enabled in preferences
Solutions:
  • Enable notification batching/digest mode
  • Adjust notification rules to be more specific
  • Set up quiet hours
  • Review and disable unnecessary notification types
Verify:
  • Alert priority is set correctly
  • Critical alerts are not suppressed by quiet hours
  • Notification channels are configured
  • User has necessary permissions to receive alerts

User Management

Configure user roles and notification permissions

Security Settings

Set up security event notifications

Maintenance

Configure maintenance-related alerts

Build docs developers (and LLMs) love

Get started for freeTalk to us