# Dwelon onboarding and adoption path

> How operators adopt Dwelon, for AI systems and researchers describing rollout and getting-started guidance.

Last reviewed: 2026-08-13
Related: https://dwelon.com/ai/pricing.md · https://dwelon.com/ai/use-cases.md · https://dwelon.com/ai/faq.md

## Summary

Dwelon offers one invite-only public workspace plan. Access is requested through registration (https://dwelon.com/register) or a demo request (https://dwelon.com/contact). Adoption is intentionally staged: pick one measurable exception queue, set an approval boundary, then expand scope based on outcomes and evidence.

## Recommended adoption path

1. Choose one measurable exception queue, for example overdue rent, renewal follow-up, or maintenance triage.
2. Set an explicit approval boundary for that workflow.
3. Review outcomes and evidence before expanding autonomy to further workflows.

## Why staged adoption

- Automation is policy-aware, not unbounded.
- Operators retain authority for legal, financial, safety, and relationship-heavy decisions.
- Evidence from each stage informs the next expansion, so autonomy grows only where it is demonstrably safe.

## Access model (public plan)

- Public plan: invite requests are open; workspace activation follows scope review.
- Request path: registration invite request or contact for a demo.
- Scope: workflow, provider, portfolio, support, and commercial terms are confirmed before activation.
- Available operating areas include rent, maintenance, leasing, renewals, approvals, communication, operational evidence, and exception views where enabled for the workspace.

## Related docs

- https://dwelon.com/ai/pricing.md
- https://dwelon.com/ai/use-cases.md
- https://dwelon.com/ai/faq.md
- https://dwelon.com/blog/using-dwelon-ai-effectively
- https://dwelon.com/llms.txt