Permissions and route lifecycle

FluentCommunity continues to own portal membership and host visibility. Social Terminal and each add-on repeat their own command, data, and capability checks. A visible menu item is never the final authorization boundary.

Managed routes register before the portal router is constructed. Disabling a destination or losing required Pro access retires publication cleanly without deleting the owning configuration. Re-enabling should adopt the same destination instead of creating duplicates.

Community event adapters use official hooks and replay-safe event identities. Native FluentCommunity points and levels remain FluentCommunity data; Cointacted Gamification balances and rankings remain Gamification data.

Test a guest, normal member, content owner, restricted member, and administrator for every enabled destination.