Accounts, tenants and solutions
Account → Tenant → Solution → Component. What is set higher up applies below; initiatives carry the work.
A freelancer or agency with several clients
Give each client its own tenant: its own members, rules, demands, portfolio board and solutions, so one client never sees another's requests or plans. Your account ties the tenants together — switch between them in the top bar, and My overview (All my solutions) shows your work across all of them. Keep your own products in a tenant of their own. The time report splits your time by solution and by initiative, for billing each client by change.
Levels
| Level | Holds |
|---|---|
| Account | The organisation; tenants; account-wide standards, glossary, agent policy baseline, drift thresholds, roles |
| Tenant | Its own members, solutions, settings and knowledge; the portfolio of demands and initiatives |
| Solution | The product or system governed: its components, design, tests, knowledge and agent connections |
| Component | A part of the solution (web app, mobile app, service): its repositories, code modules and technical design |
Initiatives
An initiative answers one or more demands and holds the requirements and work for that change. Each solution also has a quarterly maintenance initiative for defects.