Articles
A branch is a place your company does business from — a store, warehouse, plant or office. OpenJanela uses it to answer one question everywhere: whose is this? Whose order, whose purchase order, whose ticket, whose numbers on the report. Every company has at least one branch and exactly one of them is the Home […]
A branch is a physical location that raises and fulfils orders — typically a store, warehouse or office. OJ Setup → Product Setup → Company Branches holds the branch list on the left; everything on the right belongs to whichever branch is selected. Exactly one branch is flagged as the main office. What, where, who, […]
Three places to set up text your company shows or sends: Announcements and Messages are tabs of Administration and Setup → Company Preferences (Messages is also under Administration and Setup → OJ Setup → REPORTS → Messages & Documents), and automatic emails and alerts are built in Administration and Setup → Notifications. What, where, who, […]
Company Preferences are the system-wide settings under Administration. Many also show an info (ⓘ) tooltip in the admin screen. Order-status fields (onhold, ordered, confirmed, …) hold the internal status id used for that workflow stage rather than a user toggle. What, where, who, when, why What The field reference for the system-wide Company Preferences settings: […]
Your own company’s name, logo, contact details, document messages and ship/bill addresses are set under Administration and Setup → Company Preferences, on the Title and Address tabs. Press Edit, change, then Save. Other tabs are described in Company Preferences — field reference. What, where, who, when, why What The Title and Address tabs of Company […]
User Management is where administrators create the people who log in, decide which company and branch each one belongs to, and grant the permissions that gate what they can see and do. This chapter covers the screen and the data it writes; User rights & groups explains the permission model, and Permission visibility covers hiding […]
A right (permission) controls one capability — confirm an order, view price, edit a user, and so on. This chapter explains how rights are organised and how they are assigned. What, where, who, when, why What The permission model behind the user screens: individual rights (one capability each) and groups — reusable bundles of rights […]