Permissions
Two people open Xchange and see different things: Xchange knows eleven permissions, and each login brings its own selection of them. This page says which exist, what each one allows and how you notice that you are missing one.
The case
Thursday morning at Cambira Sanitärtechnik GmbH. At 8:57 AM, A. Vogt added the missing row to the value table "Zahlungsarten Webshop"; the draft is Version 8 and complete. Now it is to take effect.
Vogt opens Configuration Snapshots and looks in vain for an action that would activate Version 8. The list is there, Version 7 is in it as active, Version 8 as draft — but the action is missing.
M. Brandt opens the same screen and has it.
The difference lies in the permissions: Vogt may build drafts, Brandt may activate.
| A. Vogt | M. Brandt | |
|---|---|---|
| Connections, Routes, Value Tables | change | view |
| View Configuration Snapshots | yes | yes |
| Activate Configuration Snapshots | — | yes |
| Clarification | edit | view |
| Execution and History | view | control |
| System | — | yes |
The levels
Each permission is set for you at exactly one level:
| Level | Meaning |
|---|---|
| None | The associated area stays hidden from you; its menu item is missing. |
| Read only | You see everything in the area; changing stays locked. |
| Full | You see and change. |
Activation and Object Mappings know only None and Full. All others have all three.
The levels are independent of each other. Read only on the routes and Full on the value tables is an ordinary combination — exactly what Brandt would need to maintain key conversions as well.
What the eleven permissions open
In the SAP Business One permission tree, all eleven are under UNIORG smart Xchange. Three are named differently there than on this page; the second column gives the name under which you find them in the tree.
| Permission | In the permission tree it is called | Read only shows | Full additionally allows |
|---|---|---|---|
| Connections | Connections | Menu item Connections with all connections and their fields | Create, change and delete connections |
| Routes | Routes | Menu item Routes with all routes and all their tabs | Create, change and delete routes |
| Value Tables | Mapping | Menu item Value Tables with all tables and rows | Create, change and delete value tables |
| Configuration Snapshots | Configuration — the row under which Connections, Routes, Mapping and Activation are | Menu item Configuration Snapshots with the list of all versions | — |
| Activation | Activation | — | Validate, activate or discard a draft; import a configuration; bring back an earlier or parked snapshot |
| Execution | Execution | Menu item Execution with the running and scheduled runs | Start a run, cancel a running run, push individual records afterwards with Transfer individually |
| Automation | Run state | — | Switch a route's automation, between Automation active and Automation paused |
| History | History | Menu item History with all completed runs and jobs | Cancel or reprocess a single job |
| Clarification | Clarification | Menu item Clarification with all open cases | Reprocess or close a case |
| Object Mappings | Object Mappings | — | — |
| System | System | Menu items Settings and System Status | Change settings and trigger system actions |
Configuration Snapshots and Activation are separate. Seeing the list of versions is one permission, letting one of them take effect is the other. This way one person can build the configuration and another can put it into operation — as with Vogt and Brandt.
Activation covers more than activating. Every action that decides which configuration snapshot applies depends on it — also discarding a draft that someone else created, and loading a complete configuration from a file.
Activation and Automation only unlock actions, without a menu item of their own and without a view of their own. Activation therefore offers only None and Full. For Run state Read only can be selected; the level, however, shows exactly what None shows.
Object Mappings has no effect, for views as for actions. Leave it at None.
The Overview is open to everyone. As soon as you may open Xchange, you see it.
How you recognize a missing permission
Xchange follows one consistent rule here: What only triggers an action is gone. What shows a state stays and is grayed out.
- An action appears only with the permission for it. On the Configuration Snapshots these are Validate, Activate and Discard in the Draft panel; Compare and Export Draft stay.
- A value without change permission is there and grayed out. The input field stays, its content stays readable. The same applies to a toggle that shows a set state: the automation switch on Execution stays visible and is locked, so that you can still see which route runs automatically and which is paused.
- A menu item appears only with the permission to see its area. And when all menu items of a group are missing, the group is missing.
- You only get in with at least one permission. Otherwise, instead of the UI, the message "No Permission — You do not have permission to access UNIORG smart Xchange. Please contact your administrator." appears.


When the system is halted
An action can also be missing for a second reason: the system is halted. As long as a halt locks changing, the lock applies even with full permission. The configuration stays visible — the picture is the same as with a missing permission.
A halt announces itself. It places a banner over every screen, names the reason and points to Check System Status. A missing permission comes without such a notice, and no screen shows your own permissions. If the action is missing without a banner, it is due to the permission.
The actions on System Status with which a halt can be ended stay available during the halt.
A halt can change the view while you are working; once it is over, the actions come back on their own. Permissions, on the other hand, Xchange reads only on opening: a newly granted permission takes effect only when you open Xchange again.
How you get a permission
Permissions are granted outside of Xchange. If you are missing one, contact your administrator.
See also
- A tour of the UI (getting started) — the menu items at a glance
- System Status (reference) — where the status is shown and what each entry there means
- Configuration Snapshots (core concept) — why building and activating are two jobs
- System status and license (core concept) — the states in which Xchange halts writing, and what still works then