A little help.
Back to your people.

Open the sign-in page and choose Forgot password? to request a reset link. Check that you entered your account email, then look in your spam folder. If a reset link has expired, request a new one. Still stuck? Email us with your username and what you see on screen.

Use the code from your authenticator app, or choose the recovery-code option during sign-in if you saved one. Each recovery code works once. In Preferences → Privacy & security, you can review signed-in devices and sign them out. Orbis may ask you to confirm your identity first. Never send us your password, authenticator codes or recovery codes.

Check Preferences → Notifications, your Do Not Disturb status and whether the conversation is muted. For desktop alerts, choose Enable on this browser in Notifications. Your browser must also allow notification permission; if it is blocked, change that in your browser’s site settings. Keep an Orbis tab open: closing every tab stops new alerts. Your device’s Focus and sound settings can also silence them. Muting alerts does not remove unread messages.

Allow microphone or camera access in your browser’s site settings, then check the device selected before joining. Make sure the device isn’t muted and check your connection. If Orbis says calling is unavailable, or the problem continues, tell us your browser, device and the exact error. You can keep using messages while you troubleshoot.

Keep each file under 10 MB, with up to six attachments per message. Uploads also have a 100 MB limit over the past 24 hours. A community channel may restrict attachments even when you can send messages. For an avatar or banner, use the image-framing tool. Include the file type and error in a support request; you don’t need to send the private file itself.

For an expired invite or channel access, ask the community’s owner or a moderator. You can block someone from their profile and review blocked people in Preferences → Privacy & security. To raise a concern with Orbis, email us the relevant username, community name and a short description of what happened. Share only the details needed to explain the issue.