Workflows & business rules

Functional workflows

Client onboarding

1. Tenant creation or activation.
2. Quota definition.
3. Activation of required system modules.
4. Company creation and storage allocation.
5. User creation and assignment to companies.
6. Module activation per company.
7. Permission assignment and group creation.
8. Backup configuration.
9. Business module launch.

Tenant administrator — daily

1. Login and possible legal document acceptance.
2. Tenant dashboard review.
3. Company and quota management.
4. User and role management.
5. Open a company.
6. Module activation and permission assignment.
7. Log, backup and reporting review.
8. Support ticket creation and tracking if needed.

Business user — daily

1. Login and company selection.
2. View authorized modules.
3. Enter or process data according to permission.
4. Receive notifications.
5. Track tasks, requests and documents.
6. View authorized reports.

Permission workflow

1. Administrator assigns user to a company.
2. Activates useful modules in the company.
3. Assigns individual permission or via group.
4. SILI calculates the effective permission.
5. User sees only authorized modules.
6. Visible actions depend on the effective level.

Backup workflow

1. Administrator opens Tenant space > Security & Backup.
2. Chooses tenant or company backup.
3. Triggers manual backup or configures scheduling.
4. Monitors status in history.
5. May request restoration according to rights and procedure.

Support workflow

1. Tenant administrator opens support center.
2. Creates ticket with module, priority, description and attachments.
3. Platform support handles or assigns the ticket.
4. Exchanges continue in the ticket thread.
5. Status evolves until resolution or closure.

Custom report

1. Authorized user opens report builder.
2. Selects module and entity to analyze.
3. Selects columns, filters, sorts and limits.
4. Runs report and reviews results.
5. Chooses visualization or exports data.
6. Saves configuration if the report will be reused.

---

Structural business rules

• Business data is linked to a company.
• Companies are linked to a tenant.
• Users belong to a tenant.
• A business user must be assigned to a company to work in it.
• Modules must be active in the company to be accessible.
• Permissions are evaluated per module and per company.
• Groups can increase the effective permission.
• The none level directly does not necessarily remove a right inherited from a group.
• Deletions are sensitive; deactivation is often preferable.
• Tenant and company backups have different scopes.
• Important operations are logged.
• Notifications do not replace permissions.
• Reports depend on data entered in the modules.
• Support tickets are linked to a tenant and must not be visible to other tenants.
• Custom reports must respect user permissions and company scope.
• Stock movements linked to sales or purchases are only applied when business conditions are met.

---

Recommendations

• Start with a controlled scope.
• Create companies before business users.
• Define a permission matrix before going live.
• Use groups for stable teams.
• Keep the number of tenant administrators low.
• Reserve admin and manager for managers.
• Test each profile before opening to users.
• Define a backup policy.
• Train managers on workflows and validations.
• Regularly check inactive accounts and sessions.