Where to go next

You’ve had your first conversation, found your way around, connected data, seen Build mode, and (maybe) set up a team. From here, the docs branch by what you do. Pick your path.

If you analyze data

Deepen your feel for the conversation itself:

• The agent — what Ronja can and can’t do, and where humans stay in control.
• Explorations — lifecycle, privacy, and sharing of your conversations.
• Standard, Deep analysis, and Build — when to reach for each mode.
• Tangents — try a side-question without derailing the main thread.
• Write notes — teach Ronja how your team works.
• Fix data issues — failed syncs and broken builds.

Then see how the teaching compounds: Teach Ronja your business shows notes, curated knowledge, and the data dictionary adding up to an agent that knows your org.

If you build

Turn repeated questions into durable assets:

• Create tables with Ronja
• Build a data app
• Create a workflow
• Schedule an automation
• Monitor runs and traces
• Create a saved agent

Then read the Go Further stories to see what these compose into — start with Ronja builds your own integration, then An app your team actually uses and Automate your Monday.

If you run the organization

Govern access, quality, and spend:

• Roles and permissions and the roles capability matrix
• Manage users and roles
• Organization settings
• Scopes and sharing — what admins approve and why.
• Credits and AI spend, then Govern AI spend
• Monitor activity and usage

If your team lives in Slack or Microsoft Teams

Bring Ronja to where the conversation already happens: Use Ronja in Slack and Teams. Pushing data in from your own systems? Send data via the API.

Keep these handy

• Glossary — every term, briefly.
• What’s the difference? — workspace vs feature, note vs knowledge, and the other pairs everyone mixes up.
• FAQ and Troubleshooting — quick answers when something looks off.
• Limits and retention — caps, windows, and how long things are kept.