Loading page
Name the direction first: receiving a friend invitation and sending one are different actions. Steam says all players can receive friend invites, while limited accounts cannot send them. A worksheet built around that distinction can explain why an incoming request does not establish outgoing capability. It also prevents a friend-invite question from turning into an unrelated purchase or workaround task.
| Situation | Direction to write | Question |
|---|---|---|
| A request appears for you | Incoming | What is actually visible? |
| You intend to invite someone | Outgoing | What account restriction applies? |
| An earlier attempt is unclear | Unconfirmed | What evidence is missing? |
These are hypothetical examples, not invitations sent during a test. Do not repeatedly contact another user to reproduce a restriction. First establish which action you mean and what your own account actually shows.
Write whether there is a request you can identify or only a memory of an attempted action. “We are already friends” and “an incoming request is visible” are different statements. Avoid skipping intermediate uncertainty because the other person’s display name looks familiar.
The account name versus player name guide helps distinguish account labels. A matching nickname does not establish identity or prove which account took an action. Keep the invitation note tied to the request you can actually identify.
Record whether the question concerns a limited account and an outgoing action. Do not interpret an incoming invitation as evidence that the outgoing restriction has disappeared. The two directions can have different conditions without being contradictory.
The limited-account access guide discusses a related account concept in another feature. Do not use it to turn this invitation worksheet into spending advice or assume every feature has the same rule. Here the task is understanding direction and the relevant restriction.
You may intend to send an invitation without having a confirmed request state. A remembered click is not the same as an identified outgoing request. Write the action you planned, what you actually observed and what remains uncertain.
If someone claims a request was sent, keep that claim distinct from what you can see in your own account. There is no need to accuse them or create repeated attempts. A clear uncertainty note is more useful than an invented explanation of why another person did or did not act.
The identity concern may matter, but a friend invitation is not an accepted trade or a confirmation of inventory movement. The recipient-impostor guide provides relevant caution about familiar-looking profiles without changing what the invitation itself proves.
Do not send items, reveal account information or contact a third party merely to resolve an unclear invitation direction. Keep account and regional restrictions intact. If the real issue is another operation, name it separately instead of using friendship status as evidence of permission.
Write a concise conclusion: incoming request visible, outgoing action restricted, or an earlier state still unconfirmed. The finding can remain limited and still explain the apparent contradiction. Do not add a spending requirement, fee or bypass proposal to make the note look complete.
If you need help with an actual unexplained state, use support evidence without secrets. Include the direction and observed result rather than private contact information. This worksheet does not send requests or change account status; it leaves the next question grounded in the actual action being discussed.
Sources checked on 3 November 2026. Verify available settings in your current client; the tables give hypothetical examples for your own checks.
What you should know before you begin.
No. Incoming and outgoing actions have different conditions for limited accounts.
Do not use repeated contact as diagnosis. Identify the direction, restriction and actual observed state first.
No. Keep friendship, identity checks and inventory operations as separate questions.
