Pages

Pages

Purpose and when to use this record

Build and publish a storefront information page with stable URL, navigation placement, content, and search metadata.

At a glance

• Identify it by: Hero Cta Label.

• Check its business context: Store.

• Why care: Store, publication, consent, payment, and fulfillment states affect what customers see and what staff must act on; check the correct store before saving.

• Why care: Availability and publication flags affect future use without erasing history. Prefer disabling an obsolete setup record when existing transactions still refer to it.

Before you begin

You need the Brisk permission for the action you are taking on pages. If a Create, Edit, or Delete control is absent, do not work around it with another user’s account; ask an administrator to review your role.

Have valid Store records ready first. Those selections determine where this Page belongs and which later screens can find it.

Create a Page

Create a Page after searching for the person, organization, item, location, or resource under alternate names and identifiers. Merge or correct an existing master record instead of creating a duplicate.

1. Select the business context first: Store.

2. Enter the required identifying and operational values: Store, and Title.

3. Review Template, Is Published, and Show In Navigation deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the Page, then confirm Hero Cta Label on its detail page before continuing.

After saving: Verify this Page in the next transaction or assignment screen before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Delete a Page

Delete this Page only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

If the record is merely obsolete, use Is Published to remove it from future use while preserving existing references.

On the confirmation page, verify Hero Cta Label. After confirmation, return to the Pages list and make sure only the intended Page was removed.

Review Page details

Use the detail page as the shared record of what this Page currently means. Verify Template before relying on it for a decision.

Follow Store to determine whether the issue is on this Page or on one of those linked records.

Next check: Verify this Page in the next transaction or assignment screen before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Edit an existing Page

Edit this Page to keep the same real-world party, item, location, or resource accurate. Do not repurpose it for a different entity after activity is attached.

1. Open the detail page. Compare Store with the supporting document or approved request.

2. Recheck Template, and Is Published. These values are most likely to change storefront visibility, customer communication, payment, or fulfillment.

3. Save the change, return to the list, and confirm that the Page now appears under the expected Template, and Is Published.

After the change: Verify this Page in the next transaction or assignment screen before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Find and review pages

Use the Pages list to find the correct record before opening or changing it. Compare Store, Title, Slug, and Summary. Records with similar names or numbers can still belong to different Store.

• Keyword search checks Title, Slug, and Nav Title.

• Narrow the list with Store filters.

• The initial order emphasizes Name, Sort Order, and Title. Select a column heading when you need a different comparison.

Open the Page whose Store, Title, Slug, and Summary match the task. If it is missing, clear the list filters and recheck Store, Template, and Is Published rather than creating a replacement immediately.

Fields and business rules

Brisk stores 18 user-relevant fields for this Page, including 1 linked-record selection and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this full reference.

What happens next

Verify this Page in the next transaction or assignment screen before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Common mistakes and troubleshooting

• The record will not save: Recheck Store, and Title and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The record saved but is not available where expected: Recheck Template, and Is Published, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.

• The values look right but the result is wrong: Open Store from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.