Security and Roles

This section explains how IntegraMon separates tenant data, scopes visibility, and distinguishes user, admin, and superadmin behavior across frontend and backend layers.

Chapters

• Role Model
• Permission Model
• Value and State Reference
• AI and LLM Operating Notes

Why this topic matters

The product does not rely on a single "role can do X" switch. Access behavior is shaped by several layers:

• role and group membership
• company scope
• superadmin global vs company mode
• tag visibility mode
• focused UI mode
• resource-specific restrictions such as payloads and custom_headers
• value states such as access, deletion, and visibility modes
• AI and LLM operating context around scope and sensitive data