How-to guide

Create and publish an announcement

Follow this guide to send time-limited internal announcements to selected staff audiences. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: AdministratorFeature: StaffPermission-aware
Jump to steps
Where to goUtilities → Announcements
Before you startThe screen or action may be hidden when your role lacks permission, the related module is inactive, or a required setting has not been configured. Ask an administrator to review access rather than using another person’s account.

What you’ll accomplish

Send time-limited internal announcements to selected staff audiences. Britixo CRM keeps the result connected to the relevant customer, staff member and operational history where the feature supports those relationships. That connection is important for search, reporting, client portal visibility and future automation.

Follow these steps

  1. Go to Utilities → Announcements and select the new or add action.
  2. Select the correct related customer, contact, project or other parent record where the form requests one.
  3. Complete the required identity, ownership and date fields for the staff.
  4. Add financial, status, visibility or permission information that applies to the workflow.
  5. Add clear notes, content, line items or attachments so another authorised user can understand the record.
  6. Check validation messages and client-visible information, then save.
  7. Go to the saved record, confirm the status and activity entry, and perform the next workflow action only after review.

Fields and decisions to review

Name and emailCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
RoleCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
DepartmentsCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
PermissionsCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
LanguageCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Active and authentication settingsCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Checks before you finish

  • Apply least-privilege access.
  • Use a unique email account.
  • Reassign work before deactivation.
  • Check whether the result should be visible to a customer contact or only to staff.
  • Confirm the final status, activity entry, generated document or notification before leaving the record.
Permission and data safetyDeletion, refunds, signature clearing, module changes, payment configuration and privacy actions can affect linked records or legal history. Use the least destructive action available and follow your organisation’s approval process.