Connection objectsJSON Configuration for any Service
Store named connection objects as validated JSON per environment — database credentials, API configs, service endpoints — with ownership-based access control.
Named Connection Objects JSON configuration per environment
An AG Grid listing all connection objects with name, type, ownership, and creation date. Add connections with a name, optional type (postgres, mysql, redis), and per-environment JSON configuration.
- AG Grid columns: Name, Type, Owner, Created
- Add Connection with fields: Name, Type, Development JSON (required), Staging JSON, Production JSON
- Row click opens edit mode with read-only ID and pre-populated JSON fields
- Connections ordered alphabetically by name within organization
Real-Time JSON Validation validate as you type
Each environment value is a JSON textarea with real-time validation. Invalid JSON shows a red error message; valid JSON shows green confirmation. Values must be JSON objects, not arrays or primitives.
- Monospace textareas for JSON entry with 4-row height
- Real-time validation with red error for invalid JSON
- Green "Valid JSON" confirmation for valid input
- Validates that value is a JSON object, not an array or primitive
Ownership-Based Access creator owns, admins override
The same ownership-based access control as secrets. Creators own their connections, only owners or Admin/SuperAdmin can modify, and non-owners see a warning banner with disabled fields.
- Creator becomes owner with full modify and delete permissions
- Admin and SuperAdmin override ownership for management
- Non-owners see amber warning: "Only {owner} can modify this connection"
- Delete confirmation requires typing "delete" exactly
Organization-Scoped Storage soft deletes, unique names
All connections are filtered by current organization with unique name constraints enforced at the database level. Deleted connections use soft deletes, remaining in the database with isDeleted flags.
- Organization-scoped: all connections filtered by current organization
- Unique name constraint enforced per organization at database level
- Soft deletes: deleted connections set isDeleted but remain in database
- Role-based access: Integrator, Admin, or SuperAdmin