SAP Business One · U.S. REMOTE ROLE DESIGN

Use the B1 Web Client to give branches and mobile roles only the work they need

The browser interface reduces desktop-client deployment across sales, purchasing, inventory, finance, service and reporting roles. MTC maps identity, devices, networks, printing and add-ons so each user gets a tested remote-work setup.

Test a Real User Role→

Last reviewed · June 2026

SAP Business One Web Client gives browser-based roles direct access to the same B1 company data. MTC tests each required task, authorization, report, device and add-on in the target release, then defines the right browser and desktop mix for every role.

Start with six common remote-work groups

MTC uses this role-design shortlist to move the right work into the browser while preserving the deeper desktop functions each team needs.

Customer Operations

Review quotes and orders
Maintain authorized customer fields
Route commercial approvals
Check fulfillment status

Purchasing

Review and approve purchase orders
Confirm selected receipts
Access vendor information
Review purchasing activity

Warehouse Visibility

Check inventory by location
Request or review transfers
Support physical-count work
Look up item records

Controller Access

Review permitted journal activity
Inspect A/R and A/P
Support reconciliation review
Run authorized reports

Service Teams

Work with service calls
Look up equipment and customers
Review contract information
Check service activity

Management Review

Open role-based dashboards
Monitor assigned KPIs
Drill into supported reports
Review exceptions away from the office

Use both clients deliberately

Dimension	Web Client	Desktop Client
Endpoint	Supported browser and responsive interface	Installed Windows client
Best use	Selected day-to-day and approval workflows	Broader processing, configuration and administration
Role design	Publish only the work a remote role needs	Use for deep and administrative functions
Remote pattern	Secure browser access through the deployed architecture	Usually requires managed endpoint or remote-access design
Business records	Works with the B1 company data	Works with the same B1 company data
Validation	Confirm required functions in the target release	Confirm add-ons and local client dependencies

Where U.S. teams usually pilot browser access

Traveling U.S. Managers

Review assigned orders, purchasing, finance or service exceptions without giving the role a full administrative desktop.

Approval and Inquiry Roles

Give occasional users the supported transactions and reports they need, with role access tested before rollout.

Branches and Remote Locations

Reduce local client installation while still planning identity, device, network, printing and integration dependencies.

U.S. Web Client Evaluation FAQ

Does the Web Client create a separate copy of B1 data?

No. It works with the SAP Business One company data rather than creating another operational database. Access and supported behavior should still be validated for the proposed release and deployment.

Can a U.S. company replace the desktop client for every role?

Many day-to-day, inquiry and approval roles can move to the Web Client. MTC maps each role’s transactions, reports, add-ons, printing and administration needs, then keeps only the deeper or administrative functions on the desktop client.

How should we confirm Web Client licensing?

MTC maps each user to the appropriate SAP Business One license and confirms that the intended Web Client functions are included for the role and target release in the current proposal.

What security work remains for browser access?

Define identity, multifactor authentication where available, device and browser standards, network exposure, session policy, logging and offboarding. Browser access reduces installation work; it does not remove endpoint and access-control responsibility.

What should a U.S. branch pilot test?

Test the exact role on its real network and devices, including scanners, labels, printing, file exports, approvals and critical integrations. Record which tasks stay in the desktop client before expanding to other locations.

Demo the role—not a generic screen tour

Bring one U.S. branch, mobile manager or approval role. We will walk through its real transactions, reports, access and endpoint dependencies.

Test a User Role