Plutio Logo
Product
Work AI
TemplatesPricing
Log inTry for free
My account
Sign up
My account
Menu

Product

PricingIntegrationsFeaturesTemplates
new
Changelog
new

Support

Community
On-boarding
Help centre
Contact usStatus

Resources

Stories & SetupsAlternativesComparisonsSolutionsFree toolsMagazine

Company

AboutIn the pressBrand assetsAffiliates

Platforms

API docs
iPhone & iPad
Android
Mac & Windows
Twitter
YouTube
Instagram
Linkedin

All powered by

AI that runs your entire business as if it were you

Proposals drafted, invoices chased, clients updated - ask, and it's done.

Learn more

Close
Log inTry for free
My account
Pricing

Product

Super Work AI

Support

On-boarding
Help centre
Contact usCommunity
Status

Resources

TemplatesAPI docs
AffiliatesStories & SetupsAlternativesComparisonsFree toolsMagazineIntegrations

Company

AboutIn the pressBrand assets

Platforms

iPhone & iPad
Android
Mac & Windows

Connect

Twitter
YouTube
Instagram
Linkedin
Try Plutio free
On this page
  • What verified is
  • What verified does not do
  • What actually blocks login on Plutio
  • "I got an email saying verify your email but still can't log in"
  • When verified is actually useful
  • If a user says they can't log in
Troubleshooting
  • Common account issues
  • Email verification: what it does and does not do
  • Payment and invoice troubleshooting
  • Email and notification troubleshooting
  • Integration troubleshooting
  • File upload issues
  • Performance and loading issues
  • Permission and access issues
  • Domain registrar doesn't accept the CNAME target
  • Custom domain not working after adding CNAME
  • Your Connection is Not Private (SSL error)
  • Could not authenticate with provided details
  • Emails landing in spam or junk folder
  • Not receiving emails using your own provider
  • Can't find the delete option on an invoice
  • Invoice PDF download issues

Help Center / Troubleshooting /

Email verification: what it does and does not do

Plutio's verified flag on a user's email is informational. It is not a login gate. A user whose email shows as unverified can still log in normally, and clicking a verification link in an email does not grant login ability that was previously missing. This page explains what the flag actually is, what it does not do, and what really prevents a login when a customer reports being locked out.

What verified is

Every user in Plutio has one or more email addresses stored on their account. Each address is a small object that carries the address itself and a verified boolean, under users.emails[].verified in the database. The flag is true when we have evidence that the person who controls the inbox has interacted with a Plutio email, and false when we do not.

The flag is only written in a few narrow cases:

  • Signing in with Google. On the first Google sign-in (and on enrichment of an existing account), Plutio reads the verified_email claim returned by Google and copies it onto the matching entry in users.emails[].
  • Invitations through Auth0. When a user is created from an accepted invitation, the address is marked verified because the invite link itself proves inbox access.
  • Changing email address. When a user updates their login email, the new address is stored with verified: false until one of the conditions above applies.

Nothing else writes to this flag. There is no scheduled job that flips it, no support tool that sets it, and no path from a password reset that changes it.

What verified does not do

The most important property of the verified flag is what is not attached to it. On Plutio, verified does not gate login. A user with verified: false on every email address on file can still sign in with their password, still sign in with Google, and still resume sessions from cookies. Nothing in the login flow reads the flag.

Three pieces of the codebase are worth naming, because they are the places that would read the flag if Plutio did use it as a login gate, and none of them do:

  • Accounts configuration in app/imports/api/users/server/config/config.js sets sendVerificationEmail: false, so the Meteor Accounts framework does not auto-send a verification email at signup. The matching Accounts.validateLoginAttempt in the same file checks only whether the underlying attempt was allowed (correct password, correct handler), never the verified flag.
  • Two-factor authentication in app/imports/api/users/utils/2fa/server/login-handler.js adds a second validateLoginAttempt hook and a 2fa login handler. It checks password, 2FA state, and 2FA code. It does not read emails[].verified.
  • Google OAuth in app/imports/api/users/utils/google/server/login-handler.js is the only handler that writes the flag (line 134 when enriching an existing account, and on the creation branch when making a new user). Even here, the flag is a result of the successful Google sign-in. It is not a precondition.

In short: verified describes what we know about the inbox. It does not decide whether someone is allowed through the door.

What actually blocks login on Plutio

When a login attempt fails, one of the following is the real reason. None of them is the verified flag.

Error returnedCause
invalid_loginThe password is wrong, the email is not on any account, or the handler rejected the attempt for a generic reason. Plutio intentionally returns one shared error for these cases so the login form cannot be used to probe which emails exist.
two-factor-requiredThe account has 2FA active and the login attempt did not include a valid 6-digit code or backup code. See Two-factor authentication (2FA).
incorrect_login_verification_codeA 2FA code or backup code was provided but did not match.
pending_inviteThe email was invited to a workspace but the invitation has not been completed yet. The invite email has to be opened and the signup flow finished before login will work.
Disposable emails are not allowedTriggered by validateNewUser when an address on a known disposable-email provider tries to sign up. This is a signup gate, not a login gate: once an account exists, Plutio does not re-check the domain on every login.
account.suspended_violationThe account has been suspended (typically by the fraud pipeline or by inactivity-deletion tooling). Password validation may succeed, but every authenticated action is rejected and the user is redirected to an "Account suspended" screen. See Inactive account deletion for the inactivity case.

Those are the gates. Anything outside this list is either a workspace-level permission issue (the login succeeds but a role cannot see a particular area) or an integration-specific error (Google handshake failure, etc.) that surfaces its own message.

"I got an email saying verify your email but still can't log in"

There is one Plutio email that causes confusion here. During signup, Plutio can send an email with a 6-digit verification code. If that code has arrived but login is still failing, the situation is almost always one of these two:

  1. The code is completing a signup, not unlocking a login. The 6-digit email is sent when user.emailVerification.isPending is set on a partially-created account. Entering the code finishes the signup (it inserts the workspace person record, or lets a new workspace be created) and clears emailVerification. It does not touch users.emails[].verified. Once the signup is complete, the field is unset and nothing checks it again. If login still fails after the code is accepted, the underlying cause is one of the five gates in the previous section, not the code itself.
  2. A generic "please verify your email" message does not exist on Plutio. Meteor's built-in verification email is disabled (sendVerificationEmail: false). So if a customer describes receiving a generic verify-your-email message and blames it for a blocked login, either the email came from the signup flow above, or it came from a different service using the same email address.

Clicking any link in a Plutio email never by itself enables future logins. Either a signup is being completed, or the flag is being updated in passing, and neither of those creates or removes login ability.

When verified is actually useful

The verified flag is still worth looking at, but as a support signal, not as a login diagnostic.

  • Ownership check. If a user's primary email shows verified: true, it is strong evidence that they controlled the inbox at some point (they logged in with Google for that address, or accepted an invite sent to it).
  • Deliverability clue. A long-running account with every address verified: false has never signed in with Google and was never created through an invite. That narrows where outgoing notifications have been delivered historically.
  • Cross-reference with fraud tooling. Verified true + activity from the expected region is a positive signal; verified false + signup-time flags is neutral, not a red flag on its own.

Never use the flag to answer "why can't this user log in?". The answer to that question is always in the five gates above, plus the workspace-level permission rules described in Users and team management.

If a user says they can't log in

When a customer reports that they are locked out, work through these checks in order before doing anything else. The verified flag is deliberately absent from the list.

  1. Is the email on file at all? If not, the error is invalid_login and the next step is the password reset flow so they can type their email into the "Forgot your password?" form and see whether a reset arrives.
  2. Is 2FA active on the account? If it is and they no longer have the authenticator app or their backup codes, a proof-of-ownership reset through help@plutio.com is the only path back in. See Two-factor authentication (2FA).
  3. Is there a pending invite for this email? A user with pending_invite status needs to finish their invitation rather than log in. The original invite email contains the signup link; resend it from the admin who invited them.
  4. Is the account suspended? A suspended account can "log in" but lands on an account-suspended screen. This is the fraud or inactivity pipeline acting, not a login problem. Treat it as an account-status question.
  5. Is this a workspace-level permission issue? If login succeeds but a specific area is empty or read-only, this is a role or per-entity permission issue, not an authentication one. See Custom roles and permissions and Per-entity permissions.

Running through these in order resolves the vast majority of "I can't log in" tickets without ever needing to touch the verified flag.

Join 17,000+ businesses

★★★★★

4.6 on Capterra

No credit card required

Need help?

Workspace owners and co-owners can open a conversation with our support team from inside Plutio.

Try Plutio Free

Continue learning

More on troubleshooting

Common account issues

Most account issues come down to login credentials, two-factor authentication, or workspace access. The fixes are straightforward, and in most cases,...

Two-factor authentication (2FA)

Two-factor authentication adds a second verification step to every login, so a stolen password alone can't be used to access the workspace.

Users and team management

Users and team management covers how people are added to a Plutio workspace, what roles they can hold, how invitations work, and how access is adjusted or removed.

Inactive account deletion

Accounts that have not been logged in to for 24 months are considered inactive. Logging in once before the scheduled date keeps the account and all its data intact.

Email and notification troubleshooting

Notification delivery depends on email provider settings, notification preferences in your workspace, and in some cases, DNS configuration for custom...

Permission and access issues

Most permission issues trace back to the role that was assigned, per-entity permission settings, or an invitation that was not fully completed.

Product

PricingIntegrationsFeaturesTemplates
new
Changelog
new

Support

On-boarding
Help centre
Contact usStatus

Resources

Community
AffiliatesStories & SetupsMagazine

Company

AboutIn the pressBrand assets

Platforms

API docs
iPhone & iPad
Android
Mac & Windows

Products

ContractsDashboardsFilesFormsInboxInvoicingProjectsProposalsSchedulingTasksTimesheets

Compare

vs 17hatsvs Acuityvs Agiledvs AND.COvs Asanavs Basecampvs Bloom.iovs Bonsaivs Calendlyvs ClickUpvs Clockifyvs Copilotvs Dubsadovs Flowluvs FreshBooksvs Harvestvs HoneyBookvs HubSpotvs Indyvs Mondayvs Moxievs Notionvs PandaDocvs Paymovs Pipedrivevs QuickBooksvs Scorovs SuiteDashvs Teamworkvs Togglvs Trellovs Wavevs Wrikevs Xerovs Zoho

Alternatives

17hatsAcuityAgiledAND.COAsanaBasecampBloom.ioBonsaiCalendlyClockifyCopilotDocuSignDubsadoFlowluFreshBooksHarvestHoneyBookHubSpotIndyMondayMoxieNotionPandaDocPaymoPipedriveProposifyQuickBooksScoroSuiteDashTeamworkTogglTrelloWaveWrikeXeroZoho

Solutions

AccountantsAgenciesArchitectsBookkeepersCoachesConsultantsCopywritersDesignersDevelopersEvent PlannersFreelancersInterior DesignersLawyersMarketersMusic ProducersPhotographersPR ProfessionalsReal Estate AgentsSmall BusinessSocial Media ManagersSolopreneursTherapistsVideo ProducersVideographersVirtual AssistantsWedding PlannersWriters

Free Tools

Break-Even CalculatorContract GeneratorDiscount CalculatorDiscount Code GeneratorInvoice GeneratorLate Fee CalculatorNDA GeneratorProfit Margin CalculatorProject Budget CalculatorRate CalculatorSalary to Hourly CalculatorSavings CalculatorTax CalculatorUK Tax Calculator
Twitter
YouTube
Instagram
Linkedin
Facebook
Terms of ServiceFair Usage PolicyPrivacy PolicyCookie PolicyGDPR CommitmentData Processing AgreementSub-processorsNotice at collectionPrivacy choices
Plutio customer review signature
Plutio Logo

One app to run, grow, and automate your business with Super Work AI

Plutio customer review signature