Skip to content

Administration

Kunal Priyadarshi edited this page Oct 3, 2026 · 1 revision

Administration

This guide describes available administrative areas. Access requires an authorized role; workspace administration and platform administration are separate.

Workspace administration

Use Organisation Settings to manage organization information, membership, invitations, teams, branding, notification preferences, usage, and applicable policy settings. Follow Organization and Tenancy for ordinary team setup.

Before changing a role, confirm what work the colleague needs to do. Before enforcing MFA, ensure affected colleagues can complete authenticator setup. Before deleting data or a workspace, review retention and ownership responsibilities.

Platform administration

Eligible platform administrators can open Graphomy Administration. The current interface includes:

Area Purpose
Overview & Health View operational status and available telemetry
Tenants Directory Inspect workspace metadata and permitted tenant operations
Maintenance Mode Manage maintenance behavior
Feature Flags Control feature availability and applicable overrides
Platform Limits Manage available configuration limits
Users Directory Inspect authorized user administration information
Audit Logs Review recorded administrative activity

Review the affected tenant and the consequences before applying changes. Maintenance can affect write operations; feature changes can alter available controls. A successful settings save is not a substitute for checking the resulting user behavior.

Health and metrics can be useful to operators but may disclose operational information. Keep detailed telemetry and administrative exports out of public documentation or issue reports.

Certificates and trust

Manage signing certificates through Certificates & Trust, following the organization's trust policy. Trust-store administration belongs to eligible platform operators. Never publish private signing keys or import an unverified trust anchor just to make validation pass.

Integration readiness

Before promising production automation, confirm token provisioning, signing-service availability, email delivery, migrations, and background event dispatch and retries. See Feature Availability for observed wiring limits and Webhooks and REST API Integration for receiver behavior.

Clone this wiki locally