How-to guide

Organise knowledge base groups

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Create, reorder, colour and publish article groups.

Audience: Knowledge managerFeature: RecordPermission-aware

Plain textJump to steps

Learn with Pixie CRM

Watch this workflow

Follow real application screens at your own pace, with English captions and a matching written guide.

All video tutorials

1:37 English captions

Create and verify a knowledge base group

Create a Pixie CRM knowledge-base group with live clicks. Set its name, colour, description and order, save it and reopen the group to verify the retained settings.

Chapters & transcript Watch on YouTube

Recorded in a demonstration workspace; available options depend on your plan and permissions.
Visit the Pixie CRM YouTube channel

Where to goKnowledge Base → Manage Groups

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 this guide helps you do

Create, reorder, colour and publish article groups. Pixie 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

Go to Knowledge Base → Manage Groups and select the relevant record or setup list.
Use search, filters or status tabs to confirm you are working on the intended item.
Check linked records, activity and permissions before changing status, ownership or visibility.
Use the available edit, status, reorder, attach, copy or delete action as required.
Complete any confirmation dialog carefully; destructive actions may be restricted when linked data exists.
Check the updated state in the list and record view.
Check downstream client portal, reporting or automation effects where applicable.

Settings to check

Record title or nameCheck 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.

Related customer or recordCheck 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.

Owner or assigneeCheck 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.

StatusCheck 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.

DatesCheck 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.

Notes and attachmentsCheck 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

Verify the related record.
Use clear, searchable text.
Check visibility and permissions before saving.
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.

Browse connected topics:payment check approval service client portal notifications email customers

Was this guide useful?Your response is stored only in this browser.