General Settings

The General Settings page allows organization owners to configure the fundamental properties and preferences of their organization. This is where you manage the organization's identity and notification settings.

Accessing General Settings

Navigation Path:

User Menu → My Organizations → [Select Organization] → Settings → General

Only users with Organization Owner role can access and modify these settings.

Organization Properties Interface

The organization settings interface provides a clean, organized layout for managing your organization's fundamental properties. Here's the structure you'll encounter when accessing the General Settings page:

This interface preview shows the actual layout you'll see when visiting your organization's General Settings page. All form fields are functional and provide real-time validation feedback.

Configuration Options

Organization Name

Field	Type	Required	Description
Name	Text input	Yes	The display name for your organization shown throughout the application

Behavior:

Cannot be empty
Cannot be changed for default organizations
Max length: 255 characters
Visible to all organization members
Used in headers, reports, and user interface elements

Organization Moniker

Field	Type	Required	Description
Moniker	Text input	Yes	Unique identifier for the organization used in URLs and API calls

The moniker is a unique identifier used throughout the system. Exercise extreme caution when changing it as it involves many delicate changes to URLs, database references, and API endpoints.

Moniker Rules:

Must be unique across the entire instance
Acts as your organization's yourserver in URLs like https://yourserver/...
Cannot be changed for default organizations
Used in API endpoints and database naming
Cannot contain spaces or special characters (except hyphens and underscores)

Validation:

Alphanumeric characters allowed
Hyphens and underscores permitted
No spaces or special symbols
Case-insensitive uniqueness check

Where the Moniker is Used

The organization moniker is a fundamental identifier that permeates multiple layers of the Gigantics system. Understanding where it's used helps explain why changes to this field require extreme caution.

The moniker forms the primary component of all organization-specific URLs:

https://yourserver/main/settings/general      // Main application interface
https://yourserver/api/v1/organizations/yourorg/projects  // API endpoints
https://yourserver/dashboard/analytics         // User dashboards
https://yourserver/admin/configuration         // Administrative interfaces

Impact of Changes:

All saved bookmarks and browser history become invalid
API clients using hardcoded URLs will break
External integrations and webhooks need manual updates
User documentation containing URLs becomes outdated

API Authentication and Security

The moniker is embedded in authentication tokens and API keys:

{
  "organization": "yourorg",
  "permissions": ["read", "write"],
  "jwt_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJvcmdhbml6YXRpb24iOiJ5b3Vyb3JnIn0..."
}

Security Implications:

Changes invalidate all existing authentication tokens
Users may be logged out immediately after moniker change
API integrations with stored tokens will need re-authentication
Session management systems must be flushed
Password reset links and invitation tokens become invalid

Database and Storage Systems

The moniker is used in database naming conventions and file paths:

Database Tables:
- yourorg_projects
- yourorg_datasets
- yourorg_job_history

File Storage:
- /uploads/yourorg/datasets/
- /exports/yourorg/reports/
- /temp/yourorg/exports/

Configuration Files:
- gigantics.yourorg.config.json
- permissions.yourorg.yaml
- backups.yourorg.db

System Impact:

Database schema references may need migration scripts
File system paths are hardcoded and require renaming operations
Backup and restore procedures must be updated
Data archival systems lose track of associated files

Service Integration Points

External services use the moniker for service identification:

# Configuration Files
api_gateway:
  organization: yourorg
  endpoint_base: https://yourserver/api/v1/yourorg
 
# Service Discovery
kubernetes:
  namespace: gigantics-yourorg
  service_name: yourorg-api
 
# Container Registry
docker:
  registry: registry.yourserver.com/yourorg/

Integration Impact:

Microservice configurations need manual updates
Kubernetes deployments require namespace changes
Container registry paths must be recreated
Service mesh configurations break
Load balancer rules need updating

Monitoring and Logging Systems

Log aggregation and monitoring services group data by moniker:

Logging:
- Component: gigantics.yourorg.api
- Index: yourorg-application-logs
- Metric Prefix: gigantic_yourorg_

Monitoring:
- Dashboard: "yourorg-system-monitoring"
- Alert Rules: yourorg-high-error-rate
- Service Health: yourorg-service-checks

Observability Impact:

Historical monitoring data becomes orphaned
Log analysis queries need updating
Alert notification configurations break
Performance baselines disappear
Debugging sessions lose continuity

User Experience and Client Applications

Client applications store the moniker as configuration:

// User Preferences
{
  "userPreferences": {
    "defaultOrganization": "yourorg",
    "lastAccessed": "2024-01-15"
  }
}
 
// Browser LocalStorage
localStorage.setItem('gigantic-app-config', '{"organization":"yourorg"}');

User Impact:

Users may see "organization not found" errors
Saved work sessions and preferences reset
Browser caches contain stale configuration
Mobile app installations may require re-setup
Desktop shortcuts and favorites break

Why the Moniker Cannot Be Changed Lightly

Given the extensive usage pattern, moniker changes trigger a cascade effect:

Moniker Change Impact Chain:
1. URL invalidation → Broken bookmarks, failed API calls
2. Token invalidation → Users logged out, integrations broken
3. Database references → Migration required, data access issues
4. File system paths → Lost uploads, broken storage links
5. Service configs → Microservices failed, downtime
6. Monitoring gaps → Lost observability, debugging issues
7. User disruption → Support tickets, documentation updates

Operational Requirements for Moniker Change:

Planned Maintenance Window: Minimum 4-6 hours of downtime
Database Migration: Bulk updates to all reference tables
File System Migration: Rename all organizational directories
Service Restart: All microservices require configuration reload
User Notification: Advance notice (minimum 48 hours)
Backup Verification: Full system backup before change
Rollback Plan: Emergency revert procedure if issues occur

Best Practice Guidelines

Setting Initial Moniker:

Choose a permanent, company-registered name
Avoid abbreviations that might be confusing
Use only letters (no numbers if possible)
Consider trademark implications
Plan for scalability (avoid overly generic names)

Examples of Good Monikers:

acmecorp - Stable, company-aligned identifier
innovate-tech - Descriptive and professional
global-dynamics - Suggests scope and purpose
data-solutions-pro - Industry-specific naming

Examples of Risky Monikers:

proj2024 - Contains date, requires regular changes
team-alpha - Temporary project name
test-environment - Indicates temporary nature
admin123 - Contains temporal or sensitive information

Changing an organization moniker is equivalent to performing a full system migration. Plan accordingly and ensure comprehensive testing before implementation.

Description

Field	Type	Required	Description
Description	Text area	No	Detailed information about your organization's purpose and structure

Best Practices:

Use this field to explain your organization's mission
Include information about team structure or project categories
Helpful for new members understanding the organization's context
Supports multi-line text and up to 1000 characters
Common organizational purposes (technical, administrative, compliance-focused)

Email Configuration

Field	Type	Required	Description
Email	Email input	No	Corporate email address for organization notifications

Email Functionality:

All organization-level notifications are routed to this address
Used for system alerts, security notifications, and administrative messages
Optional field - if not set, notifications may be disabled or go to individual users
Must be a valid email format
Can be changed at any time by organization owners

Common Use Cases:

Security alerts and authentication notifications
System maintenance notices
Billing or licensing communications
Administrative notifications about project activities

Organization Deletion

Permanent Action: Deleting an organization cannot be undone. Make sure you have backups of all important data before proceeding.

The Delete Organization button allows permanent removal of the organization and all associated data.

Before Deletion

⚠️ Pre-deletion Checklist:

Ensure all critical project data is exported and backed up
Notify all organization members of the impending deletion
Verify that you have any necessary compliance or audit data preserved
Confirm you have admin rights (only organization owners can delete)

What Gets Deleted

When an organization is deleted, the following are permanently removed:

All projects within the organization
All datasets, rules, and job configurations
All user assignments and role configurations
All organization-specific settings and preferences
All dictionary data and transformation history
All database connections and credentials

What Gets Preserved

Individual user accounts (they don't get deleted)
Global system settings
Other organizations on the same instance
Any shared or exported data that was saved outside the organization

Security and Permissions

Access Control

Only users with the Organization Owner role can:

View the General Settings page
Modify organization properties
Access the deletion functionality
Change the organization moniker

Audit Trail

All changes to organization settings are:

Logged with user, timestamp, and previous values
Visible in organization audit logs
Cannot be hidden or deleted by regular users

Field Restrictions

Setting	Can be Modified by	Notes
Name	Organization Owner	Cannot be changed for default org
Moniker	Organization Owner	Cannot be changed for default org
Description	Organization Owner	Always editable
Email	Organization Owner	Always editable
Deletion	Organization Owner	Requires confirmation