## Recognizing the Different Alert Types on Screen
In Sherkety ERP & Website Platform, alerts do not all appear in the same place. The first thing to check is **where the message shows up**. If you click **Save**, **Publish**, **Update**, **Delete**, or **Submit** and a single field becomes highlighted, that usually means the problem is tied to that specific input. You may see text directly under or beside the field, such as a required-field message or a warning that the value is not accepted. These are field-level errors, and they usually stop the action until you correct the highlighted entry.

A different pattern appears when the issue affects the whole page or the full action. In that case, look near the top of the screen or above the form for a larger warning or error notice. This kind of message often appears after trying to save content in the admin area, update pricing details, manage SEO information, or open a page you are not allowed to access. A page-level banner can also appear when several fields need attention at once.

Dismissible notices are easier to spot because they include a visible close control. Look for a small **X**, **Close**, or similar dismiss option inside the notice box. These notices may confirm something, warn you about a partial issue, or tell you that something failed. Closing the notice only removes it from view.

If you already read [Understanding Toast Messages and Action Feedback](doc:understanding-toast-messages-and-action-feedback), think of this document as the next layer: instead of short action feedback, you are learning how to recognize more persistent warnings, errors, and notices that may need a response.

[SCREENSHOT: Example of a highlighted form field with inline error text and a page-level warning banner above the form]

## Reading Warning and Error Messages Before Retrying an Action
When an action fails or only partly completes, pause before clicking the same button again. In Sherkety ERP & Website Platform, the message itself usually tells you what kind of problem you are dealing with. Read the exact wording in the alert area first. A warning often means the action may need review or may have completed with a concern. An error usually means the action was blocked. A notice may simply confirm what happened and whether you need to do anything else.

Start by connecting the message to the button you just used. If you clicked **Save**, the message is likely about missing or invalid form entries. If you clicked **Publish**, the warning may relate to content that cannot be published yet. If you clicked **Delete**, the notice may confirm removal or explain why deletion could not continue. If you opened an admin page and saw an alert immediately, the message may be about access restrictions rather than data entry.

Next, scan the screen for supporting clues:

- Highlighted fields
- Error text under inputs
- Required-field indicators
- A warning banner above the form
- A dismissible notice near the top of the page

These visible cues help you decide whether the action was completely blocked or whether it finished with a warning. For example, if the page stays open and several fields are marked, the action likely did not complete. If a notice appears without any blocked fields, the action may have gone through but still needs your attention.

Do not rely on memory alone. If you need help from another user or an Administrator, copy the exact message text or take a screenshot while the alert is still visible.

[SCREENSHOT: A warning notice shown after clicking Save, with highlighted fields lower on the page]

## Fixing Form Errors That Block Saving or Publishing
When **Save** or **Publish** does not work, the fastest fix is to look for fields that changed appearance right after the failed attempt. In Sherkety ERP & Website Platform, blocked form actions are usually followed by visible validation feedback. A field may show an error message underneath, a colored border, or a required indicator that becomes more noticeable after you try to continue.

1. Click **Save** or **Publish** once and wait for the page to respond.
2. Scan the current section for highlighted fields, missing values, or warning text.
3. If nothing is obvious, scroll upward and check for a page-level error banner near the top of the form.
4. Return to each marked field and correct the problem.
5. Click **Save** or **Publish** again.

The correction depends on what the screen is asking for. Common fixes include entering a missing title, completing required text fields, choosing an option from a dropdown, or correcting a value that the form does not accept. In content editing screens, this may happen when a required content area is left blank. In admin pages such as **Content**, **Services**, **Pricing**, **SEO**, or **Settings**, the page may refuse to save until every required entry is complete.

If the page-level message suggests there are multiple issues, do not stop after fixing the first visible field. Scroll through the full form and check every section that appears incomplete. Some pages in Sherkety ERP & Website Platform contain several grouped inputs, so more than one problem may need attention before the button works.

After making corrections, save again and confirm that the blocking message no longer appears. If the same warning returns, reread the message and compare it with the fields still marked on screen.

## Dismissing Notices Without Missing Important Information
A dismissible notice is useful only if you read it before closing it. In Sherkety ERP & Website Platform, these notices may appear after editing content, updating admin settings, attempting a restricted action, or completing a change that needs review. Because they often disappear once dismissed, take a moment to understand what the notice is telling you.

Before selecting the close control, check whether the notice is doing one of these jobs:

- Confirming that an action completed
- Warning that something only partly completed
- Reporting that the action failed
- Pointing to a related item or status detail

If the notice mentions a page section, item name, or status result, keep it visible long enough to note that detail. This matters when you are editing website content, maintaining pricing entries, or reviewing SEO changes and need to remember exactly what the message referred to.

A common mistake is to close a warning and assume the issue is fixed. Dismissing a notice usually removes it from view only. It does not normally correct missing fields, change permissions, or retry a failed action for you. If the same notice appears again after another click, that usually means the original cause still exists.

Use the close control only after you know whether the notice was informational or action-blocking. If the notice followed a failed **Save** or **Publish**, look around the page before refreshing or trying again. If it followed a successful action, you can usually dismiss it and continue working.

[SCREENSHOT: Dismissible notice with a close icon, showing where to read the message before removing it]

## Knowing When an Alert Needs Editor Action or Administrator Help
Not every alert needs the same response. In Sherkety ERP & Website Platform, many messages can be handled directly by the person editing the page, but some alerts point to access or setup issues that need Administrator attention.

A Content Editor can usually fix alerts related to the information entered on screen. These include missing titles, incomplete required fields, empty content areas, or values that the form rejects. If the message appears after clicking **Save**, **Publish**, or **Update**, and the page highlights editable fields, start by correcting those entries yourself.

Ask an Administrator for help when the message points to something outside normal editing work. Examples include alerts about restricted access, unavailable settings, blocked admin pages, or actions you are not allowed to perform. If you try to open areas such as **Users**, **Settings**, **SEO**, **Services**, or **Pricing** and see an access-related message, the issue is likely tied to your role rather than the content on the page.

Use this quick guide:

| Alert clue on screen | Who should respond |
|---|---|
| Missing required fields or incomplete form entries | Content Editor |
| Invalid value in a field you can edit | Content Editor |
| Access denied or restricted screen message | Administrator |
| Unavailable settings or blocked admin action | Administrator |

When handing the issue to an Administrator, include two things:
- The exact alert text
- The action that triggered it, such as **Save**, **Publish**, opening **Admin Dashboard**, or entering **Users**

That information helps the Administrator understand whether the problem is about permissions, page access, or a blocked action in the admin area.

## Common Issues and How to Fix Them
Several alert patterns appear again and again in Sherkety ERP & Website Platform. Once you know what they look like, you can usually resolve them quickly.

If a required-field error appears after clicking **Save**, do not keep pressing the button. Scroll through the form and look for every field marked as required or highlighted with validation text. This is common in content editing and admin forms where one missing value can stop the full action.

If a dismissible warning keeps returning after you close it, treat that as a sign that the page still has an unresolved issue. The notice may reappear because the same incomplete step is still present. Review the page state, especially any unsaved edits, missing selections, or fields that were left blank.

If a button appears to do nothing, look more carefully at the page. The response may not be near the button itself. Check for:
- A warning banner above the form
- Inline validation text beside a field
- A notice near the top of the screen
- A blocked page message after opening an admin section

This often happens when the page responds quietly and expects you to notice the message elsewhere on screen.

If an access-related alert prevents progress, stop trying to work around it. In Sherkety ERP & Website Platform, restricted screens in the admin area are controlled by role. If you cannot enter a page or complete an action because of an access message, ask an Administrator to review your permissions.

For related guidance on short action feedback, return to [Understanding Toast Messages and Action Feedback](doc:understanding-toast-messages-and-action-feedback). That document helps you separate quick confirmation messages from the more persistent warnings and errors covered here.

## Overview
This guide focuses on the alerts in Sherkety ERP & Website Platform that need more attention than a brief popup message. You will most often see them while working in the admin area, especially on screens such as **Dashboard**, **Content**, **Users**, **Settings**, **SEO**, **Services**, and **Pricing**. They can also appear when you try to open a restricted page, save incomplete changes, publish content with missing information, or perform an action that your account is not allowed to complete.

The goal is not just to notice that “something went wrong,” but to identify the type of message and respond correctly. In practice, that means learning to tell the difference between:
- A field-level error shown next to a specific input
- A page-level warning banner shown above a form
- A dismissible notice with a close control
- An access-related alert that requires Administrator help

This document does not repeat the basics of temporary action feedback already covered in [Understanding Toast Messages and Action Feedback](doc:understanding-toast-messages-and-action-feedback). Instead, it helps you read longer-lasting warnings and errors that stay on screen until you fix the issue, dismiss the notice, or leave the page.

As you work through the sections, focus on three habits:
- Read the exact message text before retrying
- Look for highlighted fields or blocked sections on the page
- Decide whether the issue is something you can fix directly or something an Administrator must handle

These habits are especially useful when editing multilingual content, maintaining public website pages, or managing admin records where incomplete or restricted actions are easy to miss.

## Prerequisites
Before using this guidance in Sherkety ERP & Website Platform, make sure you are working in a screen where alerts can appear and that you can recognize the action that triggered the message.

You should already be comfortable with:
- Signing in to the admin area
- Opening pages such as **Dashboard**, **Content**, **Services**, **Pricing**, **SEO**, **Settings**, or **Users**
- Using buttons such as **Save**, **Publish**, **Update**, **Delete**, and **Submit**
- Noticing short feedback messages from previous actions

If you have not read the earlier document in this section, review [Understanding Toast Messages and Action Feedback](doc:understanding-toast-messages-and-action-feedback) first. That will help you separate quick action confirmations from the warnings, errors, and dismissible notices covered here.

It also helps if you can do the following before troubleshooting an alert:
- Stay on the same page after the message appears
- Scroll through the full form to find highlighted fields
- Read any text shown above the form or beside inputs
- Capture a screenshot if you may need to ask for help

You do not need special setup to follow this guide. However, some examples only apply if your account can access the admin area. If a page does not open because of a restriction message, that is itself part of the alert behavior described here.

The next document in this section is [Understanding Notification Types and What They Mean](doc:understanding-notification-types-and-what-they-mean), which explains how to interpret different notification categories across Sherkety ERP & Website Platform.