Skip to main content
Most issues in Teio can be resolved in a few minutes by following the steps below. Each section covers a specific problem and walks you through the most effective fixes in order — start at the top and work your way down. If you reach the end of a section and the problem persists, the note at the bottom tells you how to reach the support team with the right information to get things resolved quickly.

Login problems

Can’t log in to your account

If you are unable to sign in, the cause is usually a wrong password, a locked account, or a problem with your SSO provider.
1

Reset your password

On the login screen, click Forgot password? and enter the email address associated with your account. Check your inbox for a reset link — it expires after 30 minutes. If you do not see the email within a couple of minutes, check your spam or junk folder.
2

Check whether your account is locked

After five consecutive failed login attempts, Teio temporarily locks your account for 15 minutes as a security measure. Wait 15 minutes and try again. If your account remains locked after that period, contact support to have it unlocked manually.
3

Verify your SSO configuration

If your workspace uses single sign-on (SSO), make sure you are clicking Sign in with SSO and entering your work email — not your personal email. Ask your IT administrator to confirm that your account is active in your identity provider (such as Okta, Azure AD, or Google Workspace) and that the Teio application is assigned to you.
4

Try a different browser or incognito mode

Browser extensions (particularly ad blockers and password managers) can sometimes interfere with the login flow. Open an incognito or private window and try signing in again. If that works, disable your extensions one at a time in your main browser to find the one causing the conflict.
If none of these steps resolve the issue, contact support at Help → Contact support and include the email address you are trying to sign in with, the error message you see, and whether your workspace uses SSO. This allows the team to investigate your account directly.

Notification problems

Not receiving notifications

If you are missing in-app notifications, emails, or browser alerts, the issue is usually a preference setting, a spam filter, or a browser permission.
1

Check your notification preferences

Go to Settings → Notifications and confirm that the notification types you expect are enabled. Teio lets you control notifications separately for mentions, task assignments, due date reminders, and project updates — each can be set to in-app, email, or both.
2

Check your spam or junk folder

Email notifications from Teio are sent from notifications@teio.app. If they are landing in spam, mark one as “not spam” to train your email client. For consistent delivery going forward, add teio.app to your email allowlist or safe senders list.
3

Re-enable browser notification permissions

For in-browser notifications, your browser must have permission to show alerts from Teio. In your browser settings, search for Notifications (or Site permissions) and confirm that app.teio.app is set to Allow. If it is set to Block, change it and then reload Teio.
4

Check whether Do Not Disturb is active

Teio’s Do Not Disturb mode silences all notifications for a set period. Click your avatar and look for a moon icon or “DND active” indicator. If Do Not Disturb is on, click Turn off to resume notifications immediately.
If you are on a team plan, your workspace Admin may have configured notification defaults that override your personal settings. Check with your Admin if your preferences appear correct but notifications are still not arriving.

Integration problems

Integration not syncing

When an integration stops updating or shows stale data, the most common causes are an expired authentication token, a permissions change on the connected account, or a temporary rate limit.
1

Reconnect the integration

Go to Settings → Integrations and find the affected integration. If you see a warning icon or a “Reconnect” button, click it and complete the authorization flow again. This refreshes the access token and is often all that is needed.
2

Verify permissions on the connected account

Some integrations require specific permissions in the external tool. For example, the GitHub integration needs read access to your repositories, and the Google Drive integration needs access to the files you want to attach. Check the connected account in the external service and confirm that Teio still has the required permissions.
3

Check for rate limit messages

If you are syncing a large volume of data, the external service may have applied a temporary rate limit. In Settings → Integrations, click the integration name to view its sync log. A rate limit error will appear there. Wait 15–60 minutes and the sync will resume automatically once the limit resets.
4

Disconnect and reconnect from scratch

If reconnecting does not help, click Disconnect on the integration, wait 30 seconds, and then set it up again as if it were new. This clears any cached state that might be causing the problem.
If the integration continues to fail after reconnecting, contact support and include the integration name, the error shown in the sync log, and the name of the connected account. Attach a screenshot of the sync log if possible.

Performance problems

Page not loading or running slowly

Slow load times and unresponsive pages are usually caused by a stale cache, a browser issue, or temporary platform load. Follow these steps before assuming there is a widespread outage.
1

Check the Teio status page

Visit status.teio.app to see whether there is an ongoing incident or scheduled maintenance. If an incident is posted, the team is already working on it and you will see updates there. You can subscribe to status updates by clicking Subscribe to updates.
2

Hard-refresh the page

Press Ctrl+Shift+R on Windows/Linux or Cmd+Shift+R on Mac to force a full reload, bypassing the browser cache. This resolves most cases of a page that appears stuck or displays outdated content.
3

Clear your browser cache and cookies

Open your browser settings and clear cached images, files, and cookies for app.teio.app. The exact steps vary by browser:
  • Chrome: Settings → Privacy and security → Clear browsing data
  • Firefox: Settings → Privacy & Security → Clear Data
  • Safari: Develop → Empty Caches (enable the Develop menu in Preferences → Advanced first)
After clearing, sign back in to Teio and check whether performance has improved.
4

Try an incognito window

Open an incognito or private browsing window and navigate to Teio. If the page loads normally there, a browser extension in your main session is likely causing the slowdown. Disable extensions one at a time to identify the culprit.
5

Try a different browser or device

If the problem only occurs in one browser, it is a browser-specific issue. Try Chrome, Firefox, or Edge. If the problem occurs across all browsers and devices, check the status page again — a platform-side issue may have developed since you last checked.

Invitation problems

Invitation email not received

If a teammate has not received their invitation to join your workspace, work through these steps before sending a new invite.
1

Ask the invitee to check their spam folder

Invitation emails are sent from invites@teio.app. Ask the person to search their spam, junk, or promotions folder for an email from that address. If it is there, they should mark it as not spam and click the link inside.
2

Resend the invitation

Go to Settings → Members → Pending invitations and find the invitation you sent. Click Resend to issue a new email. The original invitation link is invalidated and the new one expires after 72 hours.
3

Check whether the email domain is on an allowlist

Some corporate email systems block external messages by default. Ask the invitee’s IT administrator to add teio.app to their organization’s email allowlist (sometimes called a safe senders list or approved domains list). Once added, resend the invitation.
4

Share the invitation link directly

In Settings → Members → Pending invitations, click the Copy link icon next to the invitation. Send this link directly to the person via Slack, Teams, or any other channel. The link works the same as the emailed version.
If your workspace uses SSO, invited users must sign in through your identity provider rather than setting a Teio password. Make sure the invitee’s email address in Teio matches their email in your identity provider exactly.

Permission problems

Can’t edit or delete items

If you find yourself unable to edit a task, comment, or project item, or the edit and delete options are greyed out or missing entirely, the cause is almost always a role permission or a locked item.
1

Check your role in the workspace or project

Go to Settings → Members and confirm your role. In Teio, Viewers can only read content, Commenters can add comments but cannot edit tasks, and Members, Admins, and Owners have progressively broader edit permissions. If your role is too restrictive, ask an Admin to change it.
2

Check whether the item is locked

Admins can lock individual tasks or entire projects to prevent edits. A locked item shows a padlock icon next to its title. Only an Admin or Owner can unlock it. Reach out to your workspace Admin and ask them to unlock the item if edits are needed.
3

Check whether the project is archived

Archived projects are read-only. If the project header shows an “Archived” badge, no one can edit its contents until an Admin unarchives it. Go to Settings → Projects → Archived, find the project, and click Unarchive.
4

Confirm you are in the right workspace

If you belong to multiple workspaces, make sure you are viewing the correct one. The workspace switcher is in the top-left corner of the app. It is easy to accidentally open a project in the wrong workspace where your role may be different.
If your role appears correct and the item is not locked or archived but you still cannot edit it, contact support and include the workspace name, the item you are trying to edit, and a screenshot of the permissions error. An Admin on your account may have applied a custom permission policy that needs to be reviewed.