01What this guide helps you do
Choose how much message content is visible on a locked device.
This guide focuses on one task within mobile app. Its completion test is specific: The alert visibility fits the user's environment. Use that result to decide whether the task is finished. Opening a page, entering a value or seeing a brief notification can be part of the process without establishing the complete result.
02When to use this workflow
Use this workflow when your immediate goal is to protect notification privacy. Keep the scope limited to the relevant mobile task. If you are solving a different problem, use the related guides at the end rather than applying every action here to unrelated records.
The usual operational owner is the signed-in mobile team member. If another person owns the relevant business facts or permissions, involve that person before changing the shared record. Individual access and business authority are not always the same thing.
03Prepare the information you need
Verify the installed Communications app and the account currently signed in. The separate Alactic CRM application is a different product. Check the workspace name before reviewing data or changing settings. Keep the device's network and relevant permissions in mind, especially for notifications and file selection. An operating-system permission, an application preference and a workspace role are separate controls.
Lock-screen settings, work environment, content sensitivity.
04Find the right workspace and feature
Start from Alactic Communications mobile app. Treat this as a feature locator: the arrangement of menus can differ between the web interface and the native application. Confirm the workspace name and the relevant record before proceeding, especially if you manage more than one business or use both India and UK accounts.
The target of this task is a mobile task. Keep its identity visible while you work. A similarly named record or a previously open browser tab can otherwise make a correct action affect the wrong context.
05Understand the information on screen
| Information | What it means | Practical check |
|---|---|---|
| App version | Installed release under test | Record it in a bug report |
| Account context | Edition and workspace | Match it across devices |
| Device permissions | OS-level access and alerts | Review independently of app settings |
| Saved state | Current workspace record | Check before repeating a write |
Apply these distinctions to the specific inputs for this guide: lock-screen settings, work environment, content sensitivity. You do not need to collect every possible field in the workspace. Use the information needed to make this decision and to verify its result.
06Inspect the current state first
Look at the saved record and current app state rather than relying only on a notification preview. On a small screen, open the full details for campaign errors, recipient outcomes or profile fields. Check the version when diagnosing a difference after an update. File size alone is not a feature inventory: verify the actual workflow rather than assuming a smaller package has lost functionality.
If the intended result is already present, check whether any further action is necessary. This is particularly useful after an interrupted session or when another teammate may have completed part of the work.
07Step 1: Review preview visibility
Begin with the relevant inputs: lock-screen settings, work environment, content sensitivity. Resolve any ambiguity that would change which record or business decision the task concerns. Keep a short note of the original state if you will need to compare it later. This creates a clear starting point for the next action instead of relying on memory after several screens have changed.
08Step 2: Choose an appropriate privacy setting
Use the result of the first action as the context for this one. Check the exact label, selected value or evidence involved rather than assuming that a default matches the intended task. If you identify an inconsistency, resolve it before proceeding. Keep the change narrow enough that its effect can be understood without comparing many unrelated edits.
09Step 3: Test the locked-screen appearance
Finish by checking the observable result, not only whether the interface accepted an interaction. If the result is still pending or cannot be verified, preserve that distinction in your notes. A clearly recorded unresolved state is more useful than announcing completion and discovering the missing part during a live customer task. Use the verification guidance below for the relevant feature.
10Worked example
A staff member hides detailed previews on a phone used in a public reception area.
The useful lesson is the sequence of decisions, not a promised result for every business. In this scenario, begin with “Review preview visibility”, continue with “Choose an appropriate privacy setting”, and finish with “Test the locked-screen appearance”. Compare the result with the completion test before applying the same process to a wider set of records.
Use invented names and references when practising this example. Keep the structure realistic, but do not copy a live customer conversation or payment record into training material simply to make the demonstration look authentic.
11Verify the result
Complete the task, close the keyboard and inspect the visible result. If the task changes shared workspace data, reopen the same record on the web or another authorised view when needed. Compare identical account and filter contexts. For notifications, use a controlled authorised event and check both the underlying record and the device alert; those test different parts of the experience.
The alert visibility fits the user's environment.
12Decide what to do next
| What you observe | Appropriate next step | What to avoid |
|---|---|---|
| The expected result is visibly present. | Keep the result and continue with the intended business task. | Repeating a completed action without a reason. |
| The result is still pending or uncertain. | Review the current mobile task and the relevant status. | Calling the task complete without evidence. |
| The result conflicts with the intended choice. | Revisit: Choose an appropriate privacy setting. | Changing unrelated records to hide the symptom. |
Use the observed state to choose a branch. A recovery action should address the actual cause and preserve any work that is already correct. If several people are involved, make the next owner explicit so a pending state does not become an unattended task.
13The main mistake to avoid
A useful message preview may reveal customer information to nearby people.
This mistake can make the task appear finished while leaving the business outcome unresolved. Return to the inputs and the named steps when the result is unclear. Keep a useful distinction between what you observed and what you expected. If a weaker signal is all that is available, describe the remaining uncertainty and identify how it can be checked.
14Diagnose an unexpected result
Compare the expected result with the exact current state of the mobile task. Record which of the three actions was last completed and what happened next. Keep the exact validation message or visible status where one exists. This separates an input problem from a saved-state problem and helps another person reproduce the same example.
Check the workspace, selected record and current view. Change one relevant factor at a time. If you change several unrelated settings together, a later success may not explain which change actually resolved the issue.
15Recover without duplicating work
After a network interruption, restore connectivity and inspect the saved state before repeating an action. This matters for imports, campaign confirmation and profile publication. For missing alerts, first check whether the event exists in the inbox, then review Android permissions and notification channels. Capture the app version, device context and exact symptom when a persistent issue needs support.
If the result depends on a provider or another authorised person, record that dependency and use the appropriate route. Do not simulate success by manually changing an unrelated display value or by removing evidence of the original outcome.
16Use the workflow on web and mobile
Use the text size and screen zoom needed for comfortable reading. Review controls after rotation or keyboard dismissal where relevant, and report clipped labels with the screen name and display settings. Notification previews can expose message content on a locked screen; choose visibility appropriate to the work environment. Keep the device associated with the intended individual account when it changes hands.
When comparing devices, match the same account, record and relevant filters. A desktop screenshot and a mobile screen from different contexts are not evidence of inconsistent data. If a layout problem prevents completing the task, report the screen name, device context and the affected control with private details removed.
17Keep a useful operational record
Retain only the information needed to explain the task: its purpose, the relevant mobile task, the action taken and the observed result. If the operation produced a safe reference, keep it with the time and workspace context. This makes a later handover or support query more precise than a screenshot with no explanation.
| Record | Useful content |
|---|---|
| Purpose | Choose how much message content is visible on a locked device. |
| Inputs reviewed | Lock-screen settings, work environment, content sensitivity |
| Outcome to verify | The alert visibility fits the user's environment. |
| Next owner | Signed-in mobile team member |
18Protect private information
Use the minimum customer or business information needed for the task. Restrict access to authorised colleagues, and redact unrelated names, numbers and message content when sharing a screenshot. An evidence reference is often more suitable than copying the underlying private document into a general field or support message.
For this workflow, the useful input categories are lock-screen settings, work environment, content sensitivity. They should help you make and verify the decision; they are not a reason to publish a customer database, credentials or internal operating notes. The fictional example in this guide can be used for training without exposing live records.
19Know the limits of this workflow
Phone permissions, app version, network access and workspace permissions are separate dependencies. A device notification alone is not proof of a completed business action.
Check the signed-in workspace and the latest server state before acting. Review previews carefully on the smaller screen and preserve a clear retry path when connectivity changes.
Read the linked source material for decisions controlled by a provider or by the applicable commercial terms. A practical guide explains how to approach the task; it does not add a new contractual guarantee or establish that every business use is legally suitable. Use the responsible business owner for unresolved exceptions.
20Review the process over time
Install authorised updates and verify the workflows important to your team after a meaningful change. Keep device access and notification settings under review when a phone is replaced or reassigned. A mobile and desktop discrepancy should be investigated using the same workspace, record and filters. Avoid treating a stale screen, a silent notification channel and missing server data as one undifferentiated problem.
Update related instructions when the underlying business fact or product behaviour changes. Keep a representative example from this workflow so a future revision can be compared with an explicit expectation rather than judged from memory.
21Practical questions
What should I check before starting?
Prepare lock-screen settings, work environment, content sensitivity. Then confirm the workspace and the relevant mobile task. The first action is “Review preview visibility”. Starting there keeps later decisions grounded in the correct record and avoids trying to solve a different problem with this workflow.
How do I know the task is complete?
Use this observable test: The alert visibility fits the user's environment. If a state is pending, describe it as pending. If a save or provider operation is uncertain, inspect the current record before repeating it. The result matters more than whether a button was pressed.
What if the result still does not match?
Review this risk first: A useful message preview may reveal customer information to nearby people. Keep the exact symptom, the relevant reference and the last completed action. Ask the signed-in mobile team member or the appropriate support route to review the remaining issue, using a small reproducible example rather than a broad export of customer data.
22Completion checklist
Use this checklist as a final review of the task, not as a substitute for the steps above. If an item remains unresolved, identify the next action and its owner. Do not mark a provider-dependent or unverified result complete merely because the rest of the checklist is finished.
- The intended workspace and mobile task were identified.
- The necessary inputs were reviewed: lock-screen settings, work environment, content sensitivity.
- Review preview visibility.
- Choose an appropriate privacy setting.
- Test the locked-screen appearance.
- The result was checked: The alert visibility fits the user's environment.
- The task-specific risk was considered: A useful message preview may reveal customer information to nearby people.
- Any unresolved issue has an accountable next owner and a useful evidence reference.