MuniMessage separates government verification from organization enrollment. A verified domain can establish trust, while agency policy determines which individual users may create accounts, where they belong, and what they can access.
Each organization can decide how much control is required before a new user is admitted.
Allow any user with an email address on an approved agency domain to verify that address and create a MuniMessage account directly from the login page.
Keep the domain recognized but require an administrator or designated manager to invite each person before account creation is allowed.
Restrict enrollment to selected people or departments. Enterprise identity integration also supports admission based on approved directory groups.
Identity, role, department, and partner rules continue to shape what each person can do.
Users can be limited to communication and administrative rights appropriate to their department or operating unit.
Selected users can communicate or administer across the broader organization when their responsibilities require it.
User management, organization settings, records functions, and audit access can be separated instead of giving every administrator the same privileges.
Approved users can communicate with specific partner organizations without opening the entire internal environment.
Channels provide persistent organization-managed spaces; group conversations remain ad-hoc messaging among selected participants.
Access can be changed, suspended, or revoked as people change roles, leave the organization, or no longer meet access requirements.
Verify the government organization first, then choose the enrollment policy that fits the deployment.
