Nav Links
Nav Links
Purpose and when to use this record
Define a destination within a navigation card, including its visible label, target, order, and access conditions.
At a glance
-
Identify it by: Url, Title, Description, and App.
-
Why care: These master records supply defaults and choices to later transactions. Correct duplicates and inactive records before staff build more activity on the wrong record.
Before you begin
You need the Brisk storespermission for the action you are taking on nav linkslinks. asIf parta ofCreate, theEdit, managementor module.Delete This generated referencecontrol is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.
Create a recordnav link

-
Select the business context first.
-
Enter the required identifying and operational values: Url, Title, and Description.
-
Review App deliberately; these choices control availability or workflow rather than merely describing the record.
-
Save the nav link, then confirm Url, Title, Description, and App on its detail page before continuing.
After saving: Open Nav Link-Card Relations and confirm the nav link appears with the intended label and availability. Keep the old value for thishistorical action.records Confirmwhen user-facingchanging stepsit beforewould approvingsplit or relabel prior reporting.
Delete a nav link
Before confirming, check for related Nav Link-Card Relations. Brisk may refuse deletion when another record depends on this one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.
On the confirmation page, verify Url, Title, Description, and App. After confirmation, return to the Nav Links list and make sure only the intended nav link was removed.
ViewReview recordnav link details
The evidence packet identifiesUse the viewdetail page as the shared record of what this nav link currently means. Verify App before relying on it for a decision.
Edit an existing nav link
-
Open the detail page. Compare the identifying information shown on the screen with the supporting document or approved request.
-
Recheck App. These values are most likely to change future transactions, defaults, assignment, pricing, and reporting.
-
Save the change, return to the list, and confirm that the nav link now appears under the expected App.
After the change: Open Nav Link-Card Relations and confirm the nav link appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.
Find and review recordsnav links

Fields and business rules
Brisk stores 4 user-relevant fields for this action.nav Confirmlink, user-facingincluding steps0 beforelinked-record approvingselections and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.
Edit
| Field | Required | What it controls |
|---|---|---|
| Url | Yes | The |
| Title | Yes | The title used for the hyperlink. |
| Description | Yes | The text displayed next to the link. |
| App | No | The app recorded for this |
What happens next
Common mistakes and troubleshooting
-
The record will not save: Recheck Url, Title, and Description and any message beside the field. A required related record may also be inactive or unavailable to your role.
-
The values look right but the result is wrong: Compare this
navpage.Deletelinka recordThe evidence packet identifieswith theview andsourcelocationdocumentfororthisapprovedaction.setupConfirmdecision,user-facingthenstepscheckbeforetheapprovingdownstreamthisscreenpage.where it is used.