Superadmin Reference

This page is the short working reference for people who operate the global platform layer.

Superadmin area matrix

Area	Why it exists	Typical responsibility	Important boundary
Companies	keep company contexts manageable across the platform	create, review, activate, or deactivate companies	not a tenant-local settings area
Global users and access	coordinate platform-level identity and ownership	assign users, review access, separate company and global roles	avoid using superadmin for normal company admin work
Identity, mail, and templates	define defaults that affect many users and flows	maintain shared mail, login, and template behavior	changes can affect several companies at once
Metrics, storage, and health	observe the health of the whole platform	review Redis, storage, host, queue, and application signals	operational readouts are not the same as tenant incidents
Worker and platform tuning	react to backlog or capacity pressure	tune processing only with clear evidence	do not use tuning as a cosmetic quick fix
AI and LLM administration	manage cross-platform AI connectivity and defaults	review model access and safe operating context	sensitive data rules still apply

Question	Usually belongs to
one tenant behaves strangely	tenant or company admin first
many companies show the same issue	superadmin or platform operations
mail, identity, or worker defaults affect several areas	superadmin
model or AI configuration has cross-platform effect	superadmin

For shared product-facing meanings around roles, masking, lifecycle, and AI-sensitive behavior, see Product Reference and Shared Product Values.

See: