# How to Change Division in Infor M3 > Source: https://netray.co/erp-help/how-to-change-division-in-infor-m3 > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer In M3 a user works in one company (CONO) and one division (DIVI) at a time. You switch for the current session from the company/division selector in the H5 client, and you change the default you land in through the user settings (MNS150). If the division you want is missing or rejected, the user lacks authority for it. ## Kind how-to ## System infor-m3 ## Erp Infor M3 ## Module Company / Division / User settings ## Query how to change division in infor m3 ## Alternate Queries - infor m3 change company - m3 switch division - m3 default division user MNS150 - m3 not authorized to division ## Applies To Infor M3 Business Engine on-prem and CloudSuite, H5 Client and Smart Office. Menu labels vary slightly by version. ## Steps ### Change the active division **Items:** - In the H5 client, open the user or session menu in the header and look for the company/division option. Pick the target company and division from the list. - If the list does not offer the division, the user is not authorized for it. Do not fight the UI, fix the authority (see below). - To change the default for future logins, open MNS150 (User) and select the user. Check the default company and division fields on the panel for settings. - Also review the other defaults on the same user record, such as default facility and warehouse, because they must belong to the new division or panels will reject them. - Sign out and back in (or restart the session) so the new defaults are read. - Verify by opening a division-specific program such as the item or customer order program and confirming the division shown in the panel header and in the data returned. - For an integration or API user, change the division it connects with in the user record the service account uses, or pass the division where the API program supports it. ## Sections ### Company versus division in M3 **Body:** M3 data is partitioned by company (CONO) and, for many tables, by division (DIVI). Company holds shared master data and the chart of accounts structure, while the division is the legal and operational unit with its own settings, currency and periods. Most transactional work, such as customer orders and purchase orders, is scoped to a division. When you change division you are not changing a view filter. You change the context that every program reads and writes. That is why a wrong division is a real risk on write transactions, and why many sites remove the right to change division from ordinary users. ### Why the division you want is missing **Body:** The common reason is authority. M3 checks the user's role and the division/company authorizations before it lets the session enter a division. If an administrator has not connected the division to the user (or to a role the user holds), the selector will not list it. Ask the security administrator to compare the user against a colleague who can enter the division. In M3 security setup you look at the user record, the roles connected to it, and the function and data authorizations on those roles. The exact program numbers differ between versions, so search for the security programs by name in the program search rather than trusting a number from a forum post. A second cause is a stale session. Defaults are read at sign-in, so an edited user record only takes effect in a new session. ### Division changes in integrations **Body:** An M3 API call runs as the user it authenticates with, so it uses that user's default company and division unless the transaction takes the values as input. Many MI programs accept a division field, but it must still be one the service user is authorized for. A frequent integration bug is a service account whose default division was changed for a human test and never restored. Calls then succeed but write to the wrong division. Keep service accounts separate from personal accounts and document their defaults. ## Pitfalls - Changing the division in the middle of a half-entered transaction. Finish or cancel the work first. - Setting a default division but leaving a default facility or warehouse from the old division, which then fails validation. - Testing a fix in a person's own session and forgetting the service account has a different default. - Giving every user the right to change division. Restrict it to people who need it, because writes land in the active division. - Assuming a program number from an older version. Confirm menu names in your own release. ## Ai Angle A read-only assistant such as ERPray can answer which users are authorized for which division, which default division each service account uses, and which orders were written in an unexpected division, by querying the live configuration and showing the query. It does not change authority. Netray can run this on-prem so the user and security data never leave your network. ## Faq ### Can I be in two divisions at the same time in M3? **Answer:** A session has one active company and division. People who work across divisions normally open a second session or switch, and reporting that spans divisions is done with reports or queries that read several divisions rather than by being in two at once. ### Where is the default division stored? **Answer:** On the user record, maintained in MNS150. The default company, division, facility and warehouse there are applied when the user signs in. ### Why does the division selector not show my division? **Answer:** Almost always authority. The user, or a role connected to the user, is not authorized for that division. A security administrator needs to connect it, then you start a new session. ### Does changing division affect running jobs? **Answer:** Interactive sessions only. Batch jobs and integrations run under the user and context they were scheduled with, so check the schedule's user rather than your own session. ## Search terms how to change division in infor m3, infor m3 change division, infor m3 change company, m3 MNS150 user default division, m3 division authority, m3 CONO DIVI, infor m3 h5 switch division, m3 default facility warehouse user --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json