UnionStack Sites
Give a local, entity or member group a focused digital experience without rebuilding the underlying relationships in another system.
Two audiences. One connected source.
UnionStack Sites supports public-facing local content and separate authenticated member experiences. Each site can reflect the organizational entity or people type it belongs to, with its own identity, domain, navigation and intended audience.
The important distinction is deliberate: a public local website is for discoverable community information; a member site begins with registration or sign-in and can expose configured, protected experiences.
Share galleries, quick links, upcoming meetings, recently added documents, leadership and contact information in a site linked to an organizational entity.
Give members a dedicated sign-in experience, including account registration and supported Microsoft or Google sign-in, for content and workflows intended for them.
Audience comparison
| Decision | Public local site | Authenticated member site |
|---|---|---|
| Primary audience | Members, prospective members, employers and the public. | Registered and signed-in members associated with the configured people type. |
| Typical content | Meetings, selected documents, leadership, galleries, quick links and contact information. | Profile, positions, meetings, configured case experiences and connected entity navigation. |
| Discovery | Designed for open web access and public communication. | Starts behind registration and authentication. |
| Source relationship | Connected to an organizational entity such as a local. | Connected to a people type and the signed-in person’s records. |
| Best fit | Public presence, local updates and dependable resource publishing. | Personal or protected member interactions that should not be openly indexed. |
A practical launch workflow
Decide whether the site serves public visitors or authenticated members. Select the organizational entity or people type behind it.
Configure the site name, logos, icon, domain, links and social profiles so visitors know whose experience they are using.
Review meetings, documents, leadership, galleries, quick links and contact information before making the public site available.
For member sites, test registration, sign-in and the records a representative member can see. Confirm protected pages are not public.
Decide who maintains records, approves public content, manages domains and tests the experience after configuration changes.
Connected publishing
Publish upcoming dates and detail pages with related documents. Maintain the meeting record where staff also work with participants and relationships.
Make selected documents discoverable through public listings while retaining a deliberate boundary between published and protected material.
Present leaders and contact details from organizational records so the public site reflects maintained terms and roles.
Share photos and home-page visual highlights connected to the site’s organization.
Configure identity, logos, icons, links and social profiles for each domain rather than forcing every local into one generic presentation.
Use a separate private experience with registration and secure sign-in, then test visibility with representative member accounts.
Buyer guidance
Before launch, decide who can publish, which records are public, how quickly changes must appear, who owns the domain and how member access will be supported.
Why it matters
A local website should not become another isolated database. By connecting sites to UnionStack entities and people types, the experience can stay aligned with organizational structure and the records behind it.
Ask to see both experiences during evaluation. Public presentation and member authentication solve different problems, and a good rollout treats them as separate audiences with shared governance.
Member portal evaluation
Use a dedicated fake member and verify the information required to establish the account and match it to the intended people record.
Test the supported sign-in paths, sign-out, return navigation and the experience when provider authorization is interrupted.
Confirm the member sees only the configured profile, position, meeting, case and entity information intended for that audience.
Test a member whose identifying information does not match. Document who resolves the issue and what evidence they require.
Change a test member’s position or entity relationship and verify the protected navigation responds as intended.
Trace a public meeting, document or leader back to its maintained source and the person responsible for publication.
From the UnionStack blog
Compare public union publishing with authenticated member experiences and plan identity, content governance, domains and support.
Read the article →Related implementation guides
Use these maintained UnionStack 2.0 guides to evaluate the workflow in detail.
Plan audience, domain, branding and connected content for UnionStack Sites.
Support Team · UnionStack 2.09 min read → Site setupGive each UnionStack Site a clear identity, dependable domain and consistent links.
Support Team · UnionStack 2.09 min read → PublishingExpose selected connected records while keeping internal information out of the public experience.
Support Team · UnionStack 2.011 min read → Member accessVerify registration, email continuation and supported identity-provider sign-in as a real member would experience them.
Support Team · UnionStack 2.010 min read →Built for connected work
Start a 30-day free trial, then plan public and member sites around your organization.
