The project was here yesterday. Now the dashboard looks empty. Before importing anything again, check the account name, workspace and role you are viewing.
Similar screens can belong to different places. An empty training workspace does not tell you what happened in production, and a viewer may see less than an administrator. Start by reading the context already on screen; you may not need to change anything.
Read the account and workspace names
Read the visible account identity and workspace name. Compare them with your existing authorized record of the account you need. You do not have to sign out, reset a password or create another account to make this first check.
For a fictional business with a training workspace and a production workspace, both dashboards may look almost identical. An empty training list is not evidence that production subscribers disappeared.
Keep any identity note private where it contains personal information. A support screenshot should reveal only what is necessary, with sensitive details redacted.
Check the item’s identity too
Names can be reused. Two lists can both be called “Newsletter,” and two projects can have the same title. Where the product exposes a stable nonsecret object identifier, compare that identifier as well as the visible name.
Treat a URL carefully. It may include a useful project ID, but it can also include session information, private share tokens or other sensitive values. Do not paste a full private address into a public search or support forum.
If the saved reference is old or ambiguous, record the uncertainty. Do not select the closest-looking object and proceed with a consequential edit.
Could your role explain the difference?
An owner, editor, viewer and customer may see different parts of the same system. A hidden control may reflect your role rather than a missing feature. Conversely, seeing an owner preview does not establish that an ordinary customer has access.
Use the role appropriate to the check. A buyer-access test needs buyer evidence; an administrative configuration review needs authorized administrative evidence. Do not promote your own role or grant access simply to make the screen match a tutorial.
Put the expected and observed context side by side
| Check | Intended context | Observed context |
|---|---|---|
| Brand or organization | The one relevant to this task | Visible organization |
| Account | Existing authorized identity | Current signed-in identity |
| Workspace | Production, training or other named scope | Current workspace |
| Object | Expected project, list or document reference | Actual object reference |
| Role | Role needed for this specific check | Current role |
| Mode | Live, draft, preview or supported test | Actual mode shown |
Do not store passwords, recovery codes or secret endpoints in the card. Its purpose is to prevent a context error, not to become a credential file.
If the account is correct but the workspace differs, stop the planned edit and use the product’s normal authorized navigation to reach the intended workspace. If your role lacks access, request the appropriate internal review rather than creating a duplicate object.
If every context field matches and the object is still absent, you now have useful evidence for a focused investigation. Record the exact missing item, time and relevant history. Avoid asserting deletion until the product’s records support it.
Compare the six rows before making a fix. If you are in the wrong workspace, use the normal navigation you are authorized to use. If the workspace is right but your role cannot see the item, ask its owner to check access. If every row matches, record the missing item and the time for a focused support request. You have narrowed the problem without creating a duplicate or changing anyone’s permissions.