Add new Access > Login troubleshooting section #29
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughA new login troubleshooting guide was added, along with supporting metadata files. Minor heading capitalization changes were made in two FAQ pages. The updates primarily introduce new documentation content and adjust metadata, with no changes to application logic or existing functionality. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
pages/access/login-troubleshooting.mdx (2)
11-45: Remove manual numbering inside<Steps>items
<Steps>automatically renders an ordered list, so prefixing each heading with “1.”, “2.” … produces duplicated numbers in the rendered output (“1. 1. Try a fresh browser tab”). Keep the headings but drop the manual indices.-### 1. Try a fresh browser tab +### Try a fresh browser tab … -### 2. Clear your cookies and site data +### Clear your cookies and site data … -### 3. Force a logout +### Force a logout … -### 4. Try an incognito window +### Try an incognito window … -### 5. Try a different browser +### Try a different browser … -### 6. Issues with two-factor authentication +### Issues with two-factor authentication
61-67: Link the support email for conveniencePlain text
support@oneleet.comisn’t automatically clickable in many markdown renderers. Use an explicitmailto:link.-If none of the above works, reach out to us via your dedicated Slack channel with us or at support@oneleet.com and share the details below so we can help resolve your issue more quickly: +If none of the above works, reach out via your dedicated Slack channel with us or at [support@oneleet.com](mailto:support@oneleet.com) and share the details below so we can help resolve your issue more quickly:
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Knowledge Base: Disabled due to Reviews > Disable Knowledge Base setting
⛔ Files ignored due to path filters (3)
public/access/troubleshooting/chrome-clear-cookies-and-site-data-1.pngis excluded by!**/*.pngpublic/access/troubleshooting/chrome-clear-cookies-and-site-data-2.pngis excluded by!**/*.pngpublic/access/troubleshooting/chrome-clear-cookies-and-site-data-3.pngis excluded by!**/*.png
📒 Files selected for processing (5)
pages/_meta.ts(1 hunks)pages/access/_meta.ts(1 hunks)pages/access/login-troubleshooting.mdx(1 hunks)pages/oneleet-agent/faq.mdx(1 hunks)pages/penetration-testing/faq.mdx(1 hunks)
🔇 Additional comments (5)
pages/access/_meta.ts (1)
1-3: Metadata entry looks goodKey matches the new page slug and keeps the casing/style consistent with existing entries. No further action needed.
pages/_meta.ts (1)
3-3: Navigation entry added correctlyThe
"access": "Access"key slots cleanly into the top-level nav without disrupting existing structure.pages/oneleet-agent/faq.mdx (1)
12-12: Heading-case tweak is harmlessCapitalisation change preserves the generated slug (
frequently-asked-questions), so inbound links remain valid.pages/penetration-testing/faq.mdx (1)
5-5: Same heading-case tweak hereSlug stability confirmed; no other content affected.
pages/access/login-troubleshooting.mdx (1)
22-27: Referenced screenshots verified – all images are present under public/access/troubleshooting.
jnfrati
left a comment
jnfrati
left a comment
There was a problem hiding this comment.
Thanks for setting this up! Leaving one small comment after that happy to approve 👍
|
Bypassing approval requirement here as I just turned off the setting that dismisses approvals when you make new commits. It's quite annoying and we don't do this on our oneleet-platform repo currently for this reason -- it delays getting changes in when you already have an approval/approvals and are just fixing a small thing or a few small things that were mentioned in comments. We have a culture of trust that if a change is significant enough to warrant another review we will ask for approval again |
Problem
We don't currently have any easily accessible login troubleshooting steps we can share with clients and their employees
Solution
Add new Access > Login troubleshooting section to our docs based roughly on what we had documented in our internal User Authentication Troubleshooting Notion doc
Screen.Recording.2025-07-28.at.6.17.58.PM.mov
Testing
Summary by CodeRabbit
Summary by CodeRabbit
New Features
Style