Notifications and Reports

Open notifications

Select the notification control in the dashboard header. In the Web UI, the panel separates active team and service notices, live task and export activity, unread items, and earlier items. The number on the bell counts unread history; a separate colored signal marks active notices or work. Community activity appears alongside account, team, task, export, and Noteboard events.

Community items can include forum replies, profile likes and comments, changelog entries, achievement unlocks, and other activity directed to your account. Select an item to open the related page when a destination is available.

Mark as read or clear

Open an unread item or use its read action to clear only that badge. Choose Mark all read to keep the list while clearing every unread badge. In the Web UI, open the panel actions menu for Clear all. These actions do not dismiss active processing, storage, or service notices. Notification settings opens account preferences.

Clearing a notification does not delete the Atlas comment, forum reply, profile comment, task, export, invitation, or message that created it. Return to that feature’s own page when you need its full history.

Invitations and message requests

A team invitation can be accepted or declined from its notification. Confirm the team name and intended role before accepting; the team will become available in the header selector after membership is active.

A first direct message arrives as a request in Messenger. Open the conversation and choose Accept to allow normal two-way messaging or Decline to reject it. Do not accept a request merely to report an unsafe or unwanted message.

Report a Messenger message

Open the conversation, use the action on the other person’s message, and choose Report. Add a concise reason that explains the problem and submit. You cannot report your own message or send duplicate reports for the same message.

A report does not automatically remove the conversation or block the sender. Decline a pending request or stop replying when continuing the conversation is unsafe. For an immediate threat or account-security issue, preserve relevant evidence and contact the appropriate support or emergency channel.

Write a useful report

Ordinary technical disagreements are usually better handled in the Forum or support channel. Use reporting for conduct or content that requires review.

• Identify what is wrong: spam, harassment, impersonation, unsafe content, or another clear concern.
• Describe the relevant context without adding unrelated private information.
• Do not edit screenshots to change their meaning; preserve dates, usernames, and the surrounding conversation when needed.
• Submit once for the exact message. Add a support request only when important context cannot fit in the report.