Verified identity.
Connected government.
Identify verifies people and connects them in a zero-trust network so government agencies know who is sending. Trust is continuously checked, and security issues require senders to verify again.
Choose Core for identity alongside your existing email security, or Complete for identity and full email security together.
Cities. Counties. State agencies. Districts. Schools. Public safety.
Who is actually behind the request?
Public directories, contracts and meeting agendas make government relationships easy to imitate. A message can look like it came from a city manager, a county counterpart or a familiar contractor. Your email security helps assess threats. Identify adds proof of the person behind the message before protected delivery.
Public officials
An urgent instruction carrying the name of a mayor, council member or city manager.
Agency counterparts
A budget packet, records request or coordination message from another jurisdiction.
Outside partners
A contractor, attorney or consultant asking staff to act on a sensitive request.
Choose the pathway that fits your agency.
Core adds verified sender identity alongside the email security your agency already uses. Complete combines identity verification and the full email-security stack in one deployment.
Verified identity before protected delivery.
This sample finance inbox shows Core verifying the sender while existing email security continues to screen for threats. With Complete, Identify also provides that email-security stack. Agency policy determines delivery, verification holds and threat isolation. All identities and activity below are simulated; a verified identity does not authorize a payment or make a message harmless.
Shared identity across participating agencies.
Government works across organizational boundaries. Identify is building a trusted communications identity network: a properly verified person and their verified affiliation can be recognized across participating cities and agencies, so each organization does not have to start from zero. Each agency decides how that identity is trusted in its own environment.
Government-to-government identity
The network pairs a verified person with their verified government affiliation. A “Verified Government Identity” indicator makes both clear when a county official writes to a city.
Verified vendors and outside partners
Contractors, attorneys, consultants, IT vendors and other partners belong in the same identity model. Recognized identity can support relationships across participating agencies.
Shared recognition. Agency control.
Agencies retain their inboxes, delivery rules and approval processes. Participation and verification establish recognition; a government-looking address alone does not.
Identity first. Your policies decide.
Core is designed to work with Microsoft 365 and Google Workspace alongside your existing email security. Configure protected communications for selected departments or individuals, with a clear path for legitimate senders and public correspondence.
External message arrives
A message is addressed to an inbox covered by the agency’s protected communications policy.
Prove the sender
Check who is actually behind the email. A familiar display name or prior relationship is not enough.
Apply the agency’s policy
Use the identity result to permit delivery or require verification and review. Existing email security continues its threat checks.
Make identity visible
Show verified sender context when the message meets policy. Keep payment, records and sensitive-request approval processes in place.
Protect the relationships government runs on.
The City Manager needs confidence in urgent instructions. The Clerk needs a workable path for public and official correspondence. IT needs clear controls. Council members need protection appropriate to the authority their names carry. Core lets your agency set that scope.
Finance, payroll & accounts payable
Verify vendors and the people making sensitive requests. Keep independent payment and bank-change approvals in place after identity is confirmed.
Clerks, permits & public works
Set verification and review policies around the way your department handles residents, contractors and official correspondence.
HR & department staff
Bring identity context to direct-deposit updates, benefits messages and requests claiming to come from a supervisor.
Police, fire & emergency management
Establish verified counterpart relationships for communication across agencies, with delivery policies suited to the department.
Schools, districts & authorities
Verify the partners, service providers and agency contacts behind routine coordination and sensitive requests.
Elected & appointed officials
Apply higher protection policies for mayors, council members, city managers, chiefs and department heads whose identities carry public authority.
Greater authority. Higher protection.
Impersonating a public official can affect staff decisions, public money and confidence in government. Identify helps your agency put stronger identity requirements around the officials and departments where those consequences are greatest.
Start with the office and its relationships
Map staff, standing vendors and agency counterparts. Prioritize verification around the people an official relies on.
Brief the official and their staff
Explain verified identity, held messages, exceptions and the process for sensitive requests in plain language.
Require verification for protected inboxes
Configure stronger identity policies for selected officials, department heads and teams, with an agreed verification and review path.
Protect the official’s identity beyond their inbox
We’re building impersonation monitoring around official communications beyond the inbox, with coordinated action when an identity’s trust status changes.
Verified identity. Ongoing accountability.
The network we’re building connects verified identity, current trust status and an authorized record of communications and security events. Core and Complete provide two deployment pathways into that shared identity foundation.
Revocation and re-verification
Suspend verified status when an identity is compromised or malicious behavior is detected. Require re-verification before restoring trust; identity is never permanent immunity.
Coordinated incident response
Propagate changes in an identity’s trust status to participating organizations that rely on it, so each agency does not have to discover the same compromise independently.
Chain of custody and audit history
Give authorized teams a record of who was verified, when, their status at the time of communication, security events, revocations and administrative actions.
An interagency identity directory
Resolve “Is this actually Jane Smith from the City of X?” against a verified identity and affiliation, independently of what an email claims.
Start with the inbox. Build trusted relationships.
Identity recognition is the shared foundation. Each agency retains its own policy and authority. Choose Core alongside your current email security or Complete for identity and full email security in one deployment.
A clear path
from briefing to protection.
An illustrative first-month plan based on Identify’s onboarding process. Your actual schedule, permissions, and go-live date are agreed with your agency.
Map the people your agency relies on.
Select the officials, departments and inboxes to protect. Map standing vendors and agency counterparts, and choose Core alongside existing security or Complete for the full stack.
Outcome: an agreed identity scope and onboarding plan.
A few practical
questions.
Clear answers for the people responsible for your agency’s communications.
Discuss your agency’s setupWhat is Identify Government?
Identify Government brings verified sender identity to protected government email. Core works alongside an agency’s existing email security; Complete combines identity and email security. The Identify network is being built to make verified people and government affiliations recognizable across participating organizations, with ongoing checks and agency-controlled policies.
Does Core replace our existing email security?
Core is designed to coexist with your current email-security provider. It adds verified sender identity before delivery to protected inboxes while your existing tools continue to screen for threats. We review how it fits your environment with IT.
How do Core and Complete differ?
Core adds verified sender identity alongside your existing email security. Complete combines the same identity foundation with Identify’s full email-security stack. They are two deployment pathways: use Core with your current provider, or deploy Complete as your email-security platform.
What happens to legitimate senders and public correspondence?
For protected inboxes, agency policy can require an unverified sender to verify before delivery. During onboarding, we agree on verification, review and exception paths for residents, new vendors and time-sensitive correspondence. Your agency decides which inboxes and departments use protected communications mode.
What if a verified sender’s account is compromised?
Verified identity does not make an account immune to compromise. Existing email security with Core—or Identify’s stack with Complete—continues to assess threats. The network we’re building adds automatic trust suspension, re-verification and shared incident response across participating organizations.
What does a verified identity indicator mean?
It communicates the sender’s verified identity context. The network’s “Verified Government Identity” indicator pairs a verified person with a verified government affiliation. It does not authorize a payment, grant access or guarantee a message is harmless. Your agency’s approval processes still apply.
Does the network share our inboxes with other agencies?
The network is built around shared identity recognition across participating organizations. Each agency retains its own inboxes and policy controls. We review identity data exchange and integration boundaries with your IT team.
What access does Identify need?
We review the Microsoft 365 or Google Workspace integration, required permissions, data flows and policy actions with your IT team before deployment. The package and protected-inbox scope determine the setup.