Sites App Overview

Sites

1. What it is

Sites lets your organisation build internal web pages — department homepages, onboarding guides, knowledge centres, executive portals — without leaving the platform. Each page is assembled from section types (hero banners, FAQ accordions, team member lists, policy links, and dozens more), and several of those sections can pull live data from other apps so the page stays current.

• Enablement: Sites requires a licence. An admin enables the app from Admin → Apps Marketplace, and it appears in the sidebar once enabled.
• What it is not: Sites is not a public-facing website builder. Pages are visible only to authenticated users inside your organisation, scoped by the audience rules you set.

2. Standing it up

1. Go to Admin → Apps Marketplace, find Sites, and enable it.
2. Open Apps → Sites → Admin → Settings and review the defaults. Most features are on by default; the two that are off — Ask This Page (Reader AI) and AI Page Metadata — can be turned on when you are ready.
3. Decide who may create sites. The Who can create a site picker defaults to Managers (manager, admin, and super admin). You can widen it to everyone or narrow it to specific groups.
4. Create the first site: click New Site from the Sites list. Give it a name, choose a type (Team, Department, Company, Project, or Knowledge Base), and add at least one page.
5. Add members. The creator is automatically the owner. Add editors (can create and edit pages) or viewers (can see draft content) from the site’s Members tab.
6. Publish the site. Until you publish, only members can see it. After publishing, every user in the organisation can browse it — unless you restrict individual pages with audience rules.

A site with no published pages is invisible to non-members. Publishing the site alone does not publish its pages; each page is published individually (or in bulk from the page list).

3. How it fits together

Sites and pages. A site is the container — it has a name, a type, a navigation bar, and members. Pages live inside a site. Each page is built from an ordered list of sections, and each section has a type that determines its layout and data shape. A site can hold up to 100 pages by default, and a business can have up to 50 sites.

Example: a “Facilities” site (type: Department) might contain three pages — “Welcome” (hero + quick links + team members), “Office Policies” (policy links + FAQ accordion), and “Floor Map” (rich text + image gallery).

Section types. There are over 50 section types. Some are static (the author fills in the content): rich text, numbered steps, data table, image gallery, FAQ accordion, timeline, file downloads. Others are live — they query platform data at render time: Policy Links pulls published policies from Policy Hub, Team Members shows users from the org chart, Form Embed renders a platform form, Calendar Events lists upcoming events, Job Listings pulls from Job Board, Org Chart draws a department hierarchy. When a linked source changes (a policy is updated, a user leaves), the governance scanner flags the page so the owner can review.

Site types. When you create a site you choose one of five types: Team, Department, Company, Project, or Knowledge Base. The type is a label that helps organise the sites list; it does not restrict what you can build inside the site.

Page types and visual modes. Each page has a type — Content, News, Wiki, Announcement, or Landing — that classifies it in search and filtering. It also has a visual mode that controls spacing and density: Utility (compact, fluid-width), Balanced (standard spacing), Editorial (generous spacing), Executive (narrow container, generous spacing), or Campaign (standard spacing, full-bleed hero).

Member roles. Each site member has one of three roles:

• Owner — full control: edit the site, manage members, delete the site. Every site must have at least one owner.
• Editor — create and edit pages, publish (subject to content review), manage page settings.
• Viewer — can see draft and unpublished content. Does not grant edit access.

Admins and Sites app-admins can do everything an owner can, across all sites.

Audience rules (page-level). By default a published page is visible to everyone. When Audience Restrictions is enabled, an editor can restrict a page to specific departments, locations, roles, job titles, job families, groups, or individual users. A restricted page with no rules is visible to admins only. Rules can also be set per section, so different viewers see different parts of the same page.

Content review. When Content Review Workflow is enabled, an editor can request review before publishing. The assigned reviewer (or any admin / Sites app-admin) approves, rejects, or requests changes. A page that has not been approved cannot be published while review is on. The Reviews tab in the sidebar shows the pending queue, badged with the count.

Self-maintaining content. Several section types — Policy Links, Team Members, Contact Cards, Org Chart, Form Embed, Calendar Events, and News Feed — are bound to live platform data. When Self-Maintaining Content is enabled, a nightly scan compares each bound section’s data to a watermark captured at publish time. If a linked policy was unpublished, a user left, or a form was deleted, the system flags the page and stages a proposed update. The owner reviews the proposal and either applies it (which republishes the page) or dismisses it. Nothing changes on a published page without a person approving.

Content expiry. When Content Expiry is enabled, you can set an expiry date on any page. Seven days before the date, the page creator is notified. On expiry day, the page is automatically archived.

Bookmarks and follows. Users can bookmark individual pages for quick access from the Bookmarks tab. When Site Follows is enabled, users can follow a site; followers are notified when a new page is published on that site. Page-level follows notify watchers when the page is updated.

Translations. When Multi-Language Translations is enabled, editors can generate AI translations of a page into any configured language. Each translation covers both the page title and section content. Translations can be verified by a second editor and are flagged as stale when the source page changes.

4. Running it

Creating a page

1. Open a site and click New Page.
2. Choose a page type (Content, News, Wiki, Announcement, or Landing) and a visual mode (Utility, Balanced, Editorial, Executive, or Campaign) that controls spacing and layout density.
3. Add sections. The AI agent can draft a page from a plain-language description, or you can add sections manually from the section gallery.
4. Preview the page with the split-screen editor, then publish.

Importing content

From the page list, click Import. Paste text or markdown, or upload a file (.md, .txt, .html, .pdf, or .docx up to 2 MB). The system converts it to native sections and creates a draft page for review.

Managing navigation

Each site has a configurable navigation bar. Go to the site’s Navigation tab to add, reorder, and nest menu items. Each item links to a page in the site or to an external URL. The bar supports horizontal or vertical layout and light or dark colour. Top-level items are capped at 10; each can have up to 15 sub-items.

Reviewing content

Open Reviews from the sidebar. The queue shows pages pending your review (across sites you are a member of, or assigned to you directly). Click a page to read it, then approve, reject, or request changes.

Bulk publishing or archiving

From the page list, select multiple pages using the checkboxes, then choose Publish or Archive from the bulk action bar. Pages that require review approval and have not been approved are skipped during bulk publish; the confirmation message shows how many were skipped.

Viewing analytics

Go to Admin → Analytics. The analytics surface shows page views, unique viewers, views by day, and the most popular pages. When AI is active, it also shows citation analytics — how often Ask AI answered a question by citing a Sites page, how many users were reached, and which pages were cited most.

Exporting sites

From the sites list, admins can export a CSV of all sites (or a filtered subset). The export includes site name, description, type, status, page count, creator, published date, and creation date.

5. Settings

All settings are at Apps → Sites → Admin → Settings.

Setting	Default	What it changes
Enable Sites AI Agent	On	The AI agent that drafts pages from conversation
Max Sites	50	Maximum sites a business can create
Max Pages per Site	100	Maximum pages in one site
Enable Page Analytics	On	View tracking and the analytics surface
Enable Page Comments	On	Threaded comments on pages
Enable Multi-Language Translations	On	AI-powered page translations with verification workflow
Enable Version History	On	Automatic version snapshots on each publish
Enable Scheduled Publishing	On	Set a future publish date on a draft page
Enable Section Templates	On	Save and reuse section designs across pages
Enable SEO & Sitemap	On	Per-site XML sitemap for internal search
Enable Content Review Workflow	On	Require reviewer approval before publishing
Enable Audience Restrictions	On	Restrict pages by department, location, role, group, or user
Enable Per-Segment Sections	On	Show different sections to different audiences on the same page
Enable Site Follows	On	Users can follow a site and get notified of new pages
Enable Stock Image Search	On	Search stock images when editing sections
Enable AI Image Generation	On	Generate images with AI when editing sections
Ask This Page (Reader AI)	Off	Readers can ask a question and get an answer grounded in the page
AI Page Metadata	Off	Auto-generate a summary and tags on each publish
Enable Content Governance	On	Periodic content governance scans (review cycle, broken links)
Self-Maintaining Content	Off	Flag and auto-draft refreshes when linked policies, forms, people, or events change
Enable Content Expiry	Off	Set expiry dates on pages; expired pages are archived automatically
Default Expiry (days)	365	Default expiry period when content expiry is on
Max Upload Size (MB)	25	Maximum file size for asset uploads
Who can create a site	Managers	Controls which roles or groups may create new sites
Notify on Page Publish	On	In-app + email notification to site followers when a page is published
Notify on New Comment	On	Notify page creator and prior commenters on new comments
Notify on Content Expiry	On	Notify page creator when a page is about to expire (7 days before)
Notify on Site Member Added	On	Notify a user when they are added to a site
Notify on Review Actions	On	Notify on review request, approval, rejection, or change request

6. More help

• Sites FAQ — specific setup and operating questions
• Ask AI — the assistant answers questions about Sites from these articles.