Browse Team & Site Management

Team & Site Management

Set your site identity and contact details

Set the public site name, description, contact details, localisation, and safe AI guidance, then verify where each value appears.

4 min readUpdated 8 Aug 2026

Goal

Give the site a clear public identity, accurate contact details, and the right localisation without publishing secrets or private information.

Before you begin

  • Use an Admin or Superadmin account.
  • Prepare the approved site name, one-sentence description, public contact channel, timezone, date format, and language.
  • Confirm which details are intentionally public.
  • Use fictional values while rehearsing.

Hazard: Treat site identity, contact, and agent-guidance fields as public. Never enter passwords, tokens, private addresses, personal phone numbers, or internal hostnames.

Open General Site Settings

  1. Open Site Settings.
  2. Choose the General tab.
  3. Review General Settings, Contact Information, and Localization before changing anything.
  4. Record the current public values so you can recover if needed.
General Site Settings groups the Site Title, display-name option, Site Description, and Agent design notes. The screenshot excludes environment-specific contact and domain values.
General Site Settings groups the Site Title, display-name option, Site Description, and Agent design notes. The screenshot excludes environment-specific contact and domain values.

Set the site title

Enter the approved public name in Site Title. Use the same spelling and capitalisation found in your brand guidance. Avoid taglines, legal suffixes, or location details unless they are part of the approved name.

Use Display Site Name when the theme should show the text name in its identity area. Review the public header after saving because themes can combine the name and branding assets differently.

Write the site description

In Site Description, explain who the site serves and what they can do in one concise sentence. Prefer plain language over a list of keywords.

  • Lead with the audience or outcome.
  • Use concrete nouns and verbs.
  • Remove internal team names and implementation details.
  • Keep page-specific campaign copy elsewhere.

Use Agent design notes safely

Agent design notes can be published to AI assistants through an installable skill. Write only stable, public guidance such as tone, audience, and preferred terminology.

SafeUnsafe
“Use concise Australian English for community readers.”API keys, passwords, tokens, or secret instructions
Approved product names and public style guidancePrivate customer, staff, or infrastructure data
Public accessibility expectationsPersonal contact details or unpublished plans

Leave the field empty when you do not have approved public guidance.

Add public contact information

Use the Email, Phone, and Address fields only for contact details approved for publication. Prefer a shared role address over a person's mailbox. If the organisation does not publish a physical address or telephone number, leave those fields empty rather than inserting placeholders.

Set localisation

ControlChoose based onVerify
TimezoneThe site's editorial and reporting timezoneScheduled and displayed dates match the intended day and time
Date FormatThe audience's familiar conventionAn unambiguous example displays correctly
Default LanguageThe primary language of the published sitePage metadata and editorial defaults match

Changing localisation can alter how existing dates are interpreted or displayed. Review time-sensitive content after saving.

Save the settings

  1. Read every changed field once more.
  2. Check that no secret, personal, or internal value is present.
  3. Save the General settings.
  4. Wait for the success confirmation before navigating away.

Verify the public identity

  1. Open the site in a private browser window.
  2. Check the header or identity area for the public name.
  3. Inspect a page that displays the description or contact details.
  4. Test the public email and telephone links without sending a message.
  5. Confirm dates and language metadata.
  6. Inspect the published AI guidance only through its supported public surface, when enabled.

Test desktop and a 390-pixel-wide viewport. Confirm no long address or contact value creates horizontal overflow.

Review consistency

Compare the site identity with the theme, SEO defaults, footer, legal pages, and account-facing site name. They can serve different purposes, but public names should not contradict one another.

Recover from a problem

  • Name appears twice: review Display Site Name and the active theme's logo/name treatment.
  • Old information remains: reload the public page and confirm the settings save completed before investigating caching.
  • Date is wrong: restore the previous timezone, then review scheduled or time-sensitive content.
  • Private information was saved: remove it immediately, save again, and follow the organisation's incident process.
  • Contact link fails: check punctuation and use a deliberately public role address.

Completion check

The approved name, description, public contact details, timezone, date format, and language display correctly; optional agent notes contain only public guidance; and a second reviewer has checked desktop and narrow output.

Publication gate: keep this guide private until an independent reviewer has confirmed every field against the current General tab and inspected the public surfaces without exposing tenant data.

Related guides