Skip to content
UnionStack logo UnionStack

Learning centre · Sites, reporting & integrations

Publish a public or member site

Plan the audience first, then connect the appropriate domain, branding and UnionStack content.

Workflow context

What this guide helps you accomplish

Plan the audience first, then connect the appropriate domain, branding and UnionStack content.

Public sites and authenticated member experiences serve different audiences. Choose the audience first, then connect the appropriate entity or people type.

Working principle
Treat public publishing and member access as separate review paths even when they share UnionStack structure.

Before you begin

Prepare the following before changing shared configuration or records:

  • A named owner for the site, report or integration and a written description of its audience and purpose.
  • Fake source records that can be published, reported or retrieved without exposing member information.
  • A review plan covering access, mobile presentation, errors and the ongoing maintenance owner.
  • An approved public-content inventory and separate fake member test identity.

Procedure

Complete the steps in order with fake or approved test information first. Record configuration decisions that will affect other teams.

01

Choose the audience

Use a public site for information intended for anyone and an authenticated member experience for information that requires sign-in.

02

Choose the connected record

Align an entity site to the relevant local or organization, or a people-type site to the intended member group.

03

Configure domain and branding

Set the domain, logo, icon, social links and identity so visitors understand whose site they are using.

04

Select content deliberately

Review meetings, documents, galleries, leadership, quick links and contact details before publishing.

05

Test member authentication separately

Test registration and supported Microsoft or Google sign-in with an authorized member account.

06

Review mobile, accessibility and privacy

Check navigation, headings, image alternatives, keyboard access, documents and small-screen layouts before launch.

Product view

UnionStack public local website populated with fake meetings, documents and leadership
UnionStack 2.0 test environment using fake data. Interface details may vary with your organization’s types, fields, permissions and terminology.

Video demonstration

Follow the principal workflow in this captioned demonstration. The recording uses fake records in the UnionStack test environment.

Troubleshooting

Use the symptoms below to diagnose the workflow before widening access, adding duplicate configuration or bypassing an intended control.

Content expected on the public home page does not appear

Check the connected entity, record status, publishing decision and relevant dates. Test as a signed-out visitor after correcting the source.

The result exposes too much or too little information

Return to the source record, audience definition and authorization rule. Correct publishing status, filters or access before changing content solely to hide the symptom.

A count or page does not match expectations

Verify source quality, status, effective dates, relationships and filters. Reproduce the result with one known record before changing the configuration.

An external connection stops working

Check ownership, authorization expiry, redirect or domain settings and recent provider changes. Rotate or reauthorize credentials through the approved secure process.

Validation checklist

Do not treat the procedure as complete until an authorized second person can reproduce the intended result.

  • The public site exposes only approved content and the member experience requires authentication for protected pages.
  • The intended audience can reach the result and an unauthorized or signed-out user cannot reach protected information.
  • Every displayed value can be traced to an understood UnionStack source record or documented calculation.
  • Mobile, keyboard, link and error-state checks have been completed.
  • An owner and recurring review date are recorded for the live site, report or integration.

Version applicability

UnionStack 2.0

This guide was verified for UnionStack 2.0 on August 16, 2026. Available fields, types, relationships, navigation and access can vary with tenant configuration and user permissions.

Continue learning

Return to the UnionStack Learning Centre, or take the UnionStack product tour to see how these parts connect.