Managing businesses, packages, and timezones
What super admins can configure at the business level and how those settings affect document operations.
Business records are rich configuration objects
A business is more than a label. The management page edits base currency, package, renewal date, country registration, timezone, approval requirement, and whether clients may edit documents.
Package settings shape onboarding and usage messaging
Client onboarding surfaces package usage and renewal windows directly. That means admin package changes are visible to end users in daily workflow, not buried in billing screens.
Approval requirements are a business switch
The business form includes an `is_need_approval` flag, so the approval workflow is partly governed at business configuration level. Documentation should call this out for multi-tenant setups.
Continue with adjacent workflows
Managing users, roles, and permissions
How access control works in practice, from role permissions to role-based menus and business-scoped data access.
Chart of accounts templates and business cloning
How account hierarchies are managed, why parent-child integrity matters, and how new businesses inherit COA templates.
Dashboard views by role
What each role sees on the main dashboard and why the dashboard is really a routing layer into operational queues.