const e = { overview: { objective: "Manage SmartStack's business application catalog (Support, Workflows, AI, etc.) and control which applications are accessible for each tenant.", problem: "SaaS platforms struggle to offer modular experience: either everyone has access to everything (too complex) or each client must negotiate a custom version (prohibitively expensive).", solution: "SmartStack organizes features into modular applications assignable per tenant, enabling fine customization without custom development." }, benefits: { automation: { title: "Complete Modularity", description: "100% of features organized in independently activatable modules per tenant" }, users: { title: "Infinite Scalability", description: "Manage as many applications as needed with granular per-tenant assignment" }, roi: { title: "Multiplier ROI", description: "3x return on investment through modular billing and reduced customization costs" } }, useCases: { uc001: "View application catalog", uc001Desc: "Visualize all available applications (system and extensions) with their status and description", uc002: "Create a custom application", uc002Desc: "Register a new business application with code, name, icon and associated modules", uc003: "Modify an application", uc003Desc: "Update an application's name, description or icon", uc004: "Enable/Disable an application", uc004Desc: "Toggle an application status to make it available or unavailable globally", uc005: "Assign applications to tenants", uc005Desc: "Define which tenants have access to which applications (e.g., Tenant A = Support + Workflows, Tenant B = Support only)", uc006: "View usage analytics", uc006Desc: "See how many tenants use each application and associated usage metrics", uc007: "Delete an application", uc007Desc: "Permanently disable a custom application no longer used", uc008: "Navigate to an application", uc008Desc: "Users access applications via navigation menu according to their permissions" }, features: { f001Title: "Context > Application > Module hierarchy", f001Desc: "Applications are organized by business context with nested modules and sections", f001Example: "Context 'platform' > Application 'administration' > Modules 'users', 'tenants', 'applications'", f002Title: "Per-tenant assignment", f002Desc: "Control which applications are visible for each tenant", f002Example: "Tenant 'Acme Corp' sees Support + Workflows, Tenant 'Beta Ltd' sees Support only", f003Title: "System vs custom applications", f003Desc: "System applications (Support, Admin, etc.) are pre-configured, custom ones created by clients", f003Example: "System app 'Support' (non-editable) + custom app 'Invoicing' (created by client)", f004Title: "Real-time usage analytics", f004Desc: "Track adoption and usage of each application per tenant", f004Example: "'Workflows' application: used by 15 tenants, 234 executions this month, 98% success", f005Title: "Built-in i18n", f005Desc: "All applications natively support translation in 4 languages (FR/EN/DE/IT)", f005Example: "'Support' application displays 'Support' in EN, 'Assistance' in FR, 'Supporto' in IT" }, faq: { q1: "What is the difference between an Application and a Module?", a1: "An Application is a grouping of business features (e.g., 'Support'). A Module is a sub-part of an Application (e.g., 'Tickets', 'Dashboard' in Support). Complete hierarchy is Context > Application > Module > Section.", q2: "Can you create custom applications?", a2: "Yes, custom applications are created via extensions. They follow the same structure as system apps (modules, sections, permissions) and can be assigned to tenants like any application.", q3: "Access works on 2 levels: 1) Application must be assigned to tenant (via Tenants > Applications), 2) User must have permission starting with application code (e.g., 'platform.support.*' to access Support).", q4: "Can applications be billed separately?", a4: "Yes, through the licensing system. Each application can have an associated cost in the license. A tenant activating an additional application pays a surcharge defined in the pricing grid." }, businessRules: { br001: "Each application must have a unique code within its context (e.g., 'platform.administration')", br002: "Applications follow Navigation hierarchy: Context > Application > Module > Section > Resource", br003: "An application must be assigned to a tenant to be visible to its members", br004: "An application can be Active (visible and assignable) or Inactive (hidden)", br005: "Extensions can register new custom applications via Applications.Create API", br006: "Application analytics aggregate usage metrics per tenant in real-time", br007: "All applications must have translations in 4 supported languages (FR/EN/DE/IT)" } }, a = {
  docsAdministrationApplications: e
};
export {
  a as default,
  e as docsAdministrationApplications
};
//# sourceMappingURL=docs-administration-applications-D3lxC1Z3.js.map
