# User journeys

![](/files/mXlP6IjuNUVhi22dRLDi)

This page explains Sudo through real user journeys. Use it when writing onboarding, product marketing, help docs, and feature walkthroughs.

## 1. New user joins Sudo

A new user usually starts with familiar communication behavior, not advanced Web3 actions.

1. Open Sudo and create or access an account.
2. Set profile information and profile photo.
3. Configure basic permissions such as notifications, camera, calls, and location.
4. Start with direct messages, search users, scan a QR code, or join a group/channel.
5. Later, create or import a wallet when they need payments, swaps, or other Web3 features.

## 2. User sends a message and follows up

1. Open recent chat inbox.
2. Choose a direct chat, group, or channel discussion.
3. Send text, media, document, location, GIF, poll, or event.
4. Use reactions, replies, quotes, edits, delete controls, pins, and starred messages to manage the thread.
5. Search inside the chat later when history grows.

## 3. User sends a crypto payment in context

1. Open a chat with the recipient.
2. Start a payment request/send flow from the composer.
3. Confirm recipient, token, network, and amount.
4. Review the transaction before signing.
5. See the transaction bubble and receipt inside the conversation.

## 4. Community creates a gated group

1. Create a new group and configure name, icon, appearance, and visibility.
2. Set admin and member permissions.
3. Connect a smart contract or token requirement if the group is gated.
4. Share invite link or QR code.
5. Use topics, reactions, mentions, and moderation tools to manage activity.

## 5. Creator grows through a channel

1. Create a channel and define branding.
2. Choose public/private visibility.
3. Share channel QR and invite links.
4. Publish broadcasts, run live streams, and link a discussion group.
5. Use channel direct messages, subscribers, admin controls, and affiliate hooks to manage the community.

## 6. Power user monitors wallet risk

1. Use Watcher bot for wallet/contract alerts.
2. Use Transaction bot for history and context.
3. Use Approvals bot to inspect approval risk.
4. Review approvals before revoking or signing.
5. Use My Tokens and My Locks bots for token state shortcuts.

## Documentation takeaway

Sudo should be documented as a connected experience: chat creates context, wallet actions create value, AI reduces complexity, and privacy/trust controls make the product usable for real users.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docx.sudochat.app/overview/user-journeys.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.