Short answer: use "logged in" (no hyphen) when it's part of a verb phrase-"I am logged in." Use "logged-in" (with a hyphen) when the two words act together as an adjective before a noun-"a logged-in user."
Quick answer
No hyphen for verb/predicate (I am logged in). Hyphenate only for a compound adjective before a noun (a logged-in user).
- Predicate/verb: no hyphen - I am logged in.
- Pre-noun modifier: hyphenate - the logged-in user.
- If a hyphen feels awkward, rewrite: users who are logged in.
Core explanation: when to hyphenate
Hyphens connect words that work together to modify a noun. When the phrase follows the verb, it remains open (two words) because it functions as a verb phrase or predicate.
- Compound adjective before a noun: hyphenate - a well-known actor, a state-of-the-art phone, a logged-in user.
- Predicate or verb phrase after the verb: keep it open - She is well known, The system is up to date, I am logged in.
Apply the same pattern to similar phrasal verbs: signed in, logged on, set up. Hyphenate only when the phrase modifies a noun directly before it.
Spacing and related forms
Some related choices matter too:
- log in (verb) - Please log in to continue.
- login (noun/adjective in some style guides) - the login page; logins (noun).
- logged in (verb phrase) vs. logged-in (compound adjective before a noun).
Pick one convention for your team or product documentation and apply it consistently.
Why writers make this mistake
Common causes:
- Sound-based guessing: the spoken phrase feels like one unit.
- Overcorrection: adding or removing hyphens without checking sentence role.
- Rushed editing: fixing a UI label and copying the form into running prose.
Real usage: wrong → right pairs you can copy
See how the correction looks in context. Each pair shows a typical misuse and the clearer alternative.
Work examples
- Wrong: Please welcome the logged in user to the team.
Right: Please welcome the logged-in user to the team. - Wrong: I am logged-in to the VPN and can't access the repo.
Right: I am logged in to the VPN and can't access the repo. - Wrong: Check for logged in employees before the rollout.
Right: Check for logged-in employees before the rollout. (Or: Check for employees who are logged in.)
School examples
- Wrong: Logged in students may submit late work.
Right: Logged-in students may submit late work. - Wrong: Are you logged-in to the class portal?
Right: Are you logged in to the class portal? - Wrong: Only logged in members can download the resource.
Right: Only members who are logged in can download the resource. (Or: Only logged-in members can download.)
Casual examples
- Wrong: I'm logged-in, call me in an hour.
Right: I'm logged in, call me in an hour. - Wrong: She left her logged in session open.
Right: She left her logged-in session open. (Or: She left her session logged in.) - Wrong: His logged in profile was visible to everyone.
Right: His logged-in profile was visible to everyone.
Try your own sentence
Test the whole sentence, not just the phrase. If the phrase follows the verb, keep it open; if it sits before a noun as a modifier, hyphenate or rewrite for clarity.
How to fix your sentence: quick rewrite steps
Three simple steps to check and fix a line:
- Identify whether the phrase is acting as a verb/predicate or as an adjective before a noun.
- Apply the rule: no hyphen for predicates; hyphen for pre-noun modifiers.
- Reread; if the hyphen feels forced, rewrite with "who are" or move the phrase after the noun.
Rewrite templates you can paste:
- Compound adjective: "logged-in [noun]" → The logged-in user reported the bug.
- Predicate (no hyphen): "[subject] is logged in" → I am logged in to the dashboard.
- Rewrite to avoid hyphenation: "[noun] who are logged in" → Users who are logged in will see the update.
Three applied rewrites:
- Original: The users logged in will get access.
Rewrite: Users who are logged in will get access. - Original: The logged in user reported a bug.
Rewrite: The logged-in user reported a bug. - Original: Are you logged-in this morning?
Rewrite: Are you logged in this morning?
A simple memory trick
Quick mental checks:
- If the phrase comes before a noun and glues the meaning together, hyphenate: logged-in users.
- If the phrase follows a verb, leave it open: they are logged in.
- If you're unsure, expand: replace "logged in N" with "N who are logged in." If that reads naturally, use no hyphen.
Similar mistakes to watch for
Once spacing or hyphenation errors appear, authors often repeat them. Watch for:
- signed in vs. signed-in
- logged on vs. logged-on
- set up (verb) vs. set-up (noun/adjective in some guides)
- login (noun) vs. log in (verb)
FAQ
Is it 'I am logged in' or 'I am logged-in'?
'I am logged in' (no hyphen). Use 'logged-in' only when it modifies a noun directly before it (a logged-in user).
Should I write 'logged in users' or 'logged-in users' in an email?
In running text, prefer 'users who are logged in' or 'the users are logged in.' Use 'logged-in users' for concise labels, headings, or UI copy where a compact adjective is appropriate.
Do the same rules apply to 'logged on' and 'signed in'?
Yes. Hyphenate when the phrase directly modifies a noun before it (the logged-on session, signed-in users); keep it open as a verb phrase.
When should I use 'login' vs 'log in'?
Use 'log in' as the verb (Please log in). Use 'login' as a noun or adjective if your style allows it (the login page). Be consistent across product and documentation copy.
Fast proofreading trick - how do I check a sentence in seconds?
Add "who is/are" after the noun or move the phrase after the noun. If the expanded form reads naturally, don't hyphenate; if not, hyphenate or rewrite for clarity.
Want a fast second opinion?
If you're unsure, paste the sentence into a checker or use the rewrite templates above to remove ambiguity. Decide one hyphenation approach for your team (UI labels vs. prose) and apply it consistently to reduce review time.