Every notification opens a specific place in the app when you tap it. Some of those places, like your dashboard, a moderation detail, or a private collection, need you signed in. When you aren't, you sign in first, then land exactly where the notification meant to take you.
When you tap
What happens depends on whether you're still signed in.
| Your sign-in | What happens |
|---|---|
| Signed in | The place it points to opens straight away. |
| Signed out, timed out, or a push opened the app from closed | You sign in first, then the page opens. The destination is held as your return point, so the trip is one continuous flow. |
Where each notification opens
After sign-in, you land on the exact place the notification pointed to rather than a generic home screen.
| Notification | Opens |
|---|---|
| Comment | The collection it's on |
| New follower | That follower's profile |
| Learning path / review | Your inbox (dedicated learning-path pages do not exist yet) |
Opening a notification marks it read, the same as any other tap.
When a push opens the app from closed
In the mobile app, tapping a push can start it up from scratch. Getting you to the right place happens in order:
- Signs you back in, using your saved sign-in when it can.
- Works out where the notification points and opens it.
- If you can't be signed back in automatically, it asks you to sign in, and the place it points to still waits for you on the other side.
If the page isn't yours to see
Signing in confirms who you are; it doesn't grant access you lack. If a page needs a role or ownership you don't have (an admin-only page, say), you'll see the standard access message after sign-in rather than the protected content.