Treat the shortcut as a signpost. Note the label you see, the folder that contains it and whether it opens, then judge the target file only after you can actually open and inspect it. If the original stays private, missing or ambiguous, write down that precise limit and stop. Do not ask for private access, and do not assume who wrote the target because of whose folder holds the pointer.
Find public social profile clues with our TraceSeek app.
Start with what the shortcut actually shows you
A shortcut is a reference that points back to an original file or folder. It can appear in a folder with a title and location you can read even when you have no permission to open the original. That is the first thing to record: the visible label, where it sits, and what happens when you try to follow it. The shortcut entry and the target are separate items, so the folder you are browsing is evidence of where a pointer is kept, not evidence of what the target contains. [Google Drive: shortcuts and original-file access]
- Write the shortcut title exactly as displayed, plus the folder path where you found it.
- Note whether following it opens a readable file, shows an access barrier, or leads to nothing.
- Do not describe the target's contents until it opens for you.
Separate the pointer from the author or owner
Because shortcut ownership and target ownership are separate, the person or team whose folder holds the shortcut is not automatically the author or owner of the original. A reference can be placed in a shared workspace by someone who is merely collecting links. Creation of a shortcut does not change the original file's permissions either, so the pointer gives you no new right to see the target. When you quote a source, attribute it to what the target itself states, not to the folder where you found the reference. [Google Drive: shortcuts and original-file access]
Several entries can point to one source
A folder may contain multiple entries that are all references to a single original. These are not independent copies, and counting them as separate sources would overstate how much evidence you have. Before treating two entries as two documents, check whether each opens to the same content. If you cannot open either target, record them as unverified references rather than as confirmed duplicates.
- Compare opened targets by their own titles and stated content, not by shortcut labels alone.
- If two shortcuts cannot be opened, list them as references of unknown status.
What to record when the original stays private
When the target is private, absent or does not open, that is a finding worth keeping. Record the date, the shortcut label, the folder it appeared in and the exact barrier you met, such as a request-access page or an empty result. Do not send access requests to the apparent owner as a way of completing the inspection, and do not fill the gap with guesses about the author or contents. The limit is the result; the unsupported inference is not.
- State plainly that the target could not be inspected, and why.
- Leave authorship, content and ownership as unknown rather than inferred.
Check access and fit before quoting
Only after the target opens should you confirm that it is the item the shortcut promised. Compare its title and content with what you expected, and quote only the version you can actually reach. If the target opens but differs from what the shortcut label suggested, treat the mismatch as a limit to note rather than smoothing it over. Options for viewing a file can vary by account and app version, so check what your own view offers before assuming a feature is available.
| observation | limit | next step |
|---|---|---|
| Shortcut title and folder are visible | Tells you nothing about the target's contents | Record the label and path, then try to open it |
| Following the shortcut displays an access barrier | The original is not available to you | Note the barrier and stop; do not request access to complete the check |
| Target opens with a different title than expected | The shortcut label and the target may not match | Quote only the opened target and note the difference |
| Two folder entries look similar | They may reference the same original | Open both before counting them as separate sources |
Keep observations and conclusions apart
A short record with three parts keeps the work honest: what you saw, what it cannot establish, and what you will do next. An observation might be that a shortcut named for a report appears in a shared folder and opens to a readable document. The limit is that the folder's owner is not thereby shown to be the author. The next step is to cite the opened document by its own title, and to leave the author unknown unless the document states it. A hypothetical case: a folder holds a shortcut labelled with an organisation's name, but the target opens as an unrelated notice. The correct note is the mismatch, not a claim about the organisation. [Google Drive: shortcuts and original-file access]
A couple more questions
Does the person whose folder holds the shortcut own or author the target file?
Not necessarily. Shortcut ownership and target-file ownership are separate, and creating a shortcut does not change the original's permissions, so the folder holder may only be referencing someone else's work.
What should I do if following the shortcut asks me to request access?
Record the barrier as your finding and stop the inspection. Requesting access to complete a citation check is not appropriate here; note that the target was not inspectable and avoid conclusions about its author or contents.
Are two shortcuts to the same file two sources?
No. Several entries can be references to one original, so open each target and compare the content before deciding how many distinct sources you actually have.
Sources & editorial notes
Official references checked on October 24, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.