Evergreen farms (pos)

Private

Project *AFC ai genetic for bench sales APPFORSOLARArrow LogisticsArtificial Intillegence  » Algo Trade Automation  » Algo Trade Manual  » Bulk mail Automation with web interface  » Bulk Mail Service For Bench Sales  » Code Generation Tool  » Cold Emailing Automation (AI-Driven)  » Invoice Inventory Automation  » invoice to inventory for evergreen  » Test Automation  » What's app Bulk messaging with AI agents  » Zelle Payment for evergreenAsk RideBowls&blendsCharan Technologies _ DevelopmentEver green Farms USA (static website)Evergreen farms (pos)Evergreen React ApplicationFinwareHackthonLucky BraidsMy Produce StandNexPumpNexZen Printer AgentNoxa_JewelleryOffice Requirments  » Daily Tasks For Madhu  » Employees requirements  » Recruitment senior mern stack developer  » Red MIne Speed  » Senior Mern Stack DeveloperOPT - (USA) UpdatesQA TestersRare FruitsRegal SolarRegal Solar DMRegal Solar Energy_ ReactReliance Home Builders_ reactRemit2AnyRestaurant POSRSVPRushi GardensRV_ EngraverSoloar AppSri Farms _ DMSri_FarmsSuthra OneSuthra QNova LabsTech FourceTechnical RequirementsTechy_DevelopmentTechy_POS Travel Matex

Tracker *Bug Feature Support Testing

Subject *

Description Edit Super Admin → Modules → Screens → Role Templates → Plan → Company → Users → Access 1. Create modules Super Admin configures POS, Landscaping, Expenses, Ecommerce and their dependencies. 2. Register screens Each page belongs to a module, with its routes, menu details and enabled status. 3. Configure role templates Select the screens and permissions available to Admin, Manager, Cashier and other roles. 4. Configure the company plan During onboarding, the selected plan determines which modules the company can use. 5. Make roles available to the company Default roles follow Super Admin templates. New templates become available dynamically. Companies can also create custom roles. 6. Assign roles to users The company assigns one or more roles to each user. 7. Resolve access after login The backend checks the current user, active role, company status, plan, modules and screen permissions. 8. Display the permitted menu and screens The frontend shows allowed pages. Backend authorization checks protect their APIs. 9. Refresh after changes Plan or permission changes refresh access automatically. Duplicate access requests are shared, recent results are reused, and Redis caches the catalog. 10. Check before deleting a role Show the affected company names and assigned users. Block deletion while users remain assigned. Reassign them, then delete the role.