Controls for shared messaging workspaces

The main application uses tenant-aware routing and authentication so organization data is resolved within the active workspace rather than a shared global view.

Yes. Role and permission checks protect campaign, contact, provider, report, billing, settings, and administration actions. Navigation also adapts to the permissions assigned to the signed-in user.

Provider requests are performed by server-side integration classes. Credentials are configured in the authenticated application and are not used to call provider APIs directly from the public landing site.

Yes. Registration, authentication, inquiry, and other public submission routes use throttling appropriate to their risk and expected traffic.